Working out why a page is missing from search

Start with the tool, not a search

Searching for your own page and finding nothing tells you very little. The URL inspection tool in Search Console tells you the actual status.

It reports whether the page is indexed, when it was last crawled, which address was chosen as canonical, and any instruction it found.

Every minute spent guessing here is wasted, because the answer is one lookup away.

Searching for a phrase from your page is also unreliable, because the engine may hold the page and simply judge another one a better answer. Absence from a result is not absence from the index.

Searching for a phrase from your page is also unreliable, because the engine may hold the page and simply judge another a better answer.

Blocked by robots

Your robots file can ask crawlers to skip a path, and one broad line can hide a whole section.

This usually happens when a staging rule survives a launch, or a folder is blocked to save crawl effort and takes real pages with it.

Fetch your own robots file and read it. It is short, it is public, and it is the fastest thing on this list to rule out.

A noindex instruction

This reliably keeps a page out. It can sit in the markup or arrive as a response header, which makes it easy to miss.

The common cause is a template or a staging setting that was never turned off. It is also the most common cause of a whole site disappearing after a relaunch.

Inspect the page and look at what the engine actually saw, rather than at what you think the template does.

It can arrive as a response header rather than in the markup, which makes it invisible in the page source and easy to hunt for in the wrong place.

Treated as a duplicate

If the engine thinks another page says the same thing, it keeps one and drops the rest. Your page may be the one dropped.

Search Console reports this plainly, including which address it chose instead.

The fix is to make the page genuinely different, or to accept the choice and stop maintaining two versions of the same thing.

Nothing links to it

An orphan page can sit in a sitemap for months without being stored, because nothing on the site suggests it matters.

Link it from the section it belongs to, from a hub page, and from any related page where the link makes sense.

This is the most common problem with pages added individually, outside the normal structure.

This is the commonest problem with pages added individually, outside the normal structure, and it is covered in orphan pages.

Too thin, or too new

A page with a heading and two sentences has little to store. Depth is not word count for its own sake, and a page has to answer something.

New sites also wait longer. A domain with little history sees pages crawled and held for weeks before a decision.

Patience is a real answer here, and it is not a satisfying one. Give it a month before rebuilding anything.

The honest question is whether somebody landing on the page would get what they came for. If the answer is that they would read it and still need to look elsewhere, no technical fix will help.

What to do in order

Inspect the page. Read the reason. Fix that one thing. Request indexing once. Then wait.

Do not change six things at once, because you will not know which worked.

Every page written by Website Builder Studio is checked for the mechanical faults on this list before anything publishes, which leaves only the judgment ones.

Keep a note of what you changed and when. Three weeks later, when it either worked or did not, that note is the difference between learning something and starting over.

Do not change six things at once. Three weeks later, when it either worked or did not, you will want to know which one mattered.

• Inspect the page in Search Console and read the stated reason
• Fix that one thing
• Request indexing once
• Note what you changed and the date
• Wait a week before touching it again
• Recheck with the tool rather than by searching