Indexing

The Indexing tab shows which of your pages Google has not indexed yet, from Search Console. Each problem is marked with what to do about it.

The four groups

• Technical: something blocks Google, such as a robots.txt rule, a noindex tag, a redirect loop or a server error. Developers fix these. See Send to developers below.
• Content: Google can read the page but chooses not to index it, for example a thin or duplicate page. A writer fixes these, usually with a refresh ticket.
• Not found by Google yet: Google does not know the address. Submit your sitemap, and check that the page is linked from other pages.
• Needs a look: the check could not decide. Open the page yourself.

Indexed pages are counted too, so you can see the total.

Check pages

Click Check pages now. The check runs in the background, so you can leave the page.

• Each run checks the next batch of up to 40 of your most important pages, by impressions.
• A page is not checked again within 24 hours.
• A full check of a large site takes several runs.

While the check runs, a banner shows at the top of the site, and other action buttons wait until it finishes. The results appear here as they come in.

Act on a problem

• Create a content ticket: for a content problem, adds a priority ticket to the ticket board.
• Send N to developers: emails every technical problem that has not been sent yet, with the page and the fix. This needs an email address for developers, set by your administrator. Once sent, the problem is marked Sent to developers.

After a fix, run Check pages now again to confirm.