Google indexing has been giving SEOs fits for the last few months. Indexing services were available that guaranteed 100% indexing of pages, however, this changed. It was Clint’s theory that this changed because the services were using the Google Indexing API and Google changed the way the API worked, forcing it to verify that either JobPosting or BroadcastEvent schema was on the page, in accordance with the TOS for the API.
By forcing this change, this eliminated the 100% indexing by indexing services. Clint tested the use of the Google API without the schema, and the pages did not index until he submitted the URLs to the search console.
Test Downloads
Transcription below:
And what the method I'm talking about is adding job posts schema to your pages in order to leverage the Google Indexing API to get your pages indexed. And the reason this is important, unless you've been living in Iraq, you may or may not know that they shut down the request for indexing feature inside of the Google Search Console. And this was in response to, although they later denied denying it was it's in response to all the indexing issues that they've had.
Coming up to this point where I can't theme is getting too many URLs, a cause the backup and etc, etc. Well, they're trying to walk that back and say that they are shutting it down, not because of caffeine, which is kind of interesting. But the the one method, or there's two methods that are working, and then there's one is the sitemap. And having dates in your sitemap, Google's actually doing a whole lot better reading the Sitemaps than they were doing before and they're indexing pages pretty much are good sites right away.
The slowest I've seen is probably a day and a half. And that's on digital year. And if you've been following the over the shoulder series, it's not a brand new site, but it's not been maintained very well. So the crawl rates really low and I'm getting stuff indexed from the sitemap just fine. The key with the sitemap is to make sure that you have an XML sitemap that has the URL and the date that the page or post was updated, the date has to be in there.
If you don't have a date in there, Google's not going to know you did it. And then they're not going to read your sitemap and they don't care. And that's despite the fact that text file Sitemaps are perfectly acceptable in a tool right now. They're just not reading the text file Sitemaps. They're using the XML ones.
Then the second way is to add job post schema to your page and then use the Google API Indexing API to submit your pages. Under the terms of service, the API is set so that it's only allowable if you have job posting schema, or video object schema with broadcast event. If you're using the job posting, and you don't have a job, you are now doing blackhat SEO, how dare you, you're a horrible person.
But this is kind of no harm no foul in the application of what we're doing. And two, if you are like I have SEO this week, for example. Technically, I can use the video object and broadcast schema and be fully in compliance with the terms of service for this API. Because I'm doing a broadcast, it's a live broadcast, but I can only use it. So this is something that you just kind of have to balance your risk. First reward or getting into catch us is the big green monster coming get you etc.
I could tell you, done this one well over 1000 pages right now. And I actually gave this method to the people at omega indexer, Elias. And that's how omega indexers getting 100% indexing. And how I'm doing is they've automated this system. Don't ask me what they did in the background, or how they figured it out. But it all works now. And then we're getting 100% indexing after three to four days. When you submit to us.
Dori: That was pretty nice of you to give it to Omega. I hope they don't share it.
Clint: No, he won't, Elias they won't. Yeah, in the people in Omega, they don't even know how I'm doing it. I just told Elias, and Elias and Christoph and then the automated it, took quite a while actually. Alright, so how do you use this? Basically, you put this schema code in your head, in this case, I just created one for SIA. And this is kind of my default for most of them now. And he just joined SIA and the job is for the testing and what you know, we pay $100 per test. So I put that in here and the max value is 1500.
You know, we have a max value, just in case. And the the idea is that since the job is their Google Indexing API is picking up the URLs and airgo indexing them. Now if you don't remember the last test if you just send it to the Google Indexing API, Google will ignore it, they've turned the switch on. And they're specifically looking for these two versions of schema, if they're not in there, you're gonna kick your URL out of their queue.
Okay, so if you have a job, that's even better, if you have a job listing, like you're looking for web designer or whatever, make one of these, put it on your sites when you're making the new pages, and then take it off after it's indexed. So that's how I've used it. To prove that it works, October 5th, I did it. And you could see I got all 10 of the test domains inside of the test pages indexed, and it took 3 days.
I submitted it here 123. And then the 3rd day, everything kicked in. After the indexing feature was shut off, I tested it again, just to make sure you can see all 10 of them actually made it in. And then as of the day, I made this, on the 27th to the domains dropped out, which is kind of normal for test pages anyway, they're not, let's be fair, they're not the highest quality. So you kind of expect that to drop out. I'm not going to reuse this again.
I didn't bother resubmitting it. But you see that the indexing works with the Google Indexing API with that in there. One thing of note is if you don't want to use this method, and you still want to use the Google Indexing API, as I said before, you can. But what you should do at the same time is you got to put it into Google Search Console, you have to submit your URL in there. And it's not doing the request indexing right now.
I haven't checked to see if you can run that through either Rich Snippets testing tool, the mobile friendly testing tool or the indexing tool, or the URL inspect tool, I mean, and just kind of like, Hey, you Google, check this out. But that might be something to look at for yourself. So right now what I would say is, if you're not going to use this, and you have a whole bunch of pages, you need to index and you need to get on omega indexer. And they figured this stuff out for you. So you're not risking your site at all. That's the safest course of action. Anyone got any questions on that?
Dori: I don't see any but I have one. So that code is just something that we can copy and paste into our pages? of course, changing the URL and some of the other, the name and things like that. Correct.
Clint: Yeah, you change the URL. Technically, you don't have to, you can copy it exactly out of your dossier if you want to use just a job. It's a really basic job post schema.
Dori: Okay, awesome.
Clint: If they wanted to, they can use this.
Dori: Perfect. Nice spying Clint. Yeah, if I have sticker, I give you one.
Clint: When everyone's complaining about indexing, I can tell you that since I've tested that I haven't had an instance where I had any issues with indexing.
Dori: And when you hear people complaining about it, you can just go hahaha. Clint: Yeah, well now at this point I do, so this is probably the last time I've talked about it because I have given dropped a lot of hints in other groups, groups that would shall not be named but they just don't know they're still fighting with indexing for some reason. So they're you go, you guys are in the know. Stay that way and keep your competition dumb.