Page not indexed Google: published but invisible, and why

Your dashboard says published. Search for the page by name and it isn't there. Both things can be true at once, for several genuinely different reasons.

"Published" means a page exists at a real address — necessary for Google to index it, nowhere near sufficient. Between "I clicked publish" and "it shows up when I search" sit several checkpoints, any one of which can quietly fail with no error message anywhere. Here is the list, in the order worth checking, and the diagnostic sequence that settles it definitively instead of guessing.

Start with the boring explanations

First: is it actually published, not quietly back in draft? Some platforms drop an edited page to draft the moment you touch it again. Second: has it simply not had time? Indexing takes days to weeks, not minutes — a brand-new page with no history anywhere waits its turn like everything else. If the page is genuinely new, the answer may simply be "give it longer" — indexing runs on the search engine's schedule, not yours.

Check whether something is telling search engines to skip it

A "noindex" flag — meant for thank-you screens, duplicates and account-only pages — left on by accident is one of the most common reasons a finished, real page never appears in search. It's also the fastest to fix, which is why it's worth checking first; a full on-page pass catches it before you ever get here. Its subtler cousin: a canonical tag pointing at a different URL says "index that one instead of this one" — useful when two addresses genuinely share content, actively harmful when it points the wrong way by mistake.

Search engines find pages by following links

A crawler doesn't magically know a URL exists; it follows links from pages it already knows, and reads the sitemap that lists the rest. A page nothing links to — reachable only by typing its exact address — is an orphan, and orphans get discovered slowly, if at all. The fix is usually simple once you look: link to the page from somewhere already being crawled, and confirm it's actually in the sitemap rather than assumed to be.

The gap between "my dashboard says published" and "the live page agrees"

Most builders keep two copies of a page: the one you edit, and a separately generated version that visitors — and crawlers — actually get. That separation is normal and useful, until the two fall out of sync: the dashboard shows the page as published while the live, crawlable version is missing it, serving an old copy, or resolving somewhere else entirely. Google indexes what it can fetch, not your dashboard's opinion of it. The tell is simple: open the real public URL in a private window, not the editor, and see what's actually there.

How to actually settle it, instead of guessing

1

Visit the real, public URL

In a private or incognito window, not logged in, not inside the editor. If the page doesn't load correctly here, nothing downstream matters yet — this is the version a crawler sees too.

2

View the page source for a noindex tag

Look for in the page's head. If it's there and you didn't put it there on purpose, that's very likely your answer.

3

Check the sitemap

Visit your site's /sitemap.xml directly and search (Ctrl/Cmd-F) for the page's URL. If it isn't listed, search engines have a much harder time discovering it exists at all.

4

Check whether anything actually links to it

Is the page reachable from your homepage, your navigation, or at least one other page's body content, within a couple of clicks? If the only way to reach it is typing the exact URL from memory, it's effectively invisible to a crawler.

5

Ask Google directly

Search Console's URL Inspection tool checks the exact URL against Google's own index and states the precise reason plainly — crawled but not indexed, discovered but not yet crawled, blocked by a tag, and so on — rather than leaving you to infer it. It's free, it's Google's own tool, and it's the single most reliable way to stop guessing at this point.

6

If none of the above explains it, wait

Some pages simply haven't had their turn yet, particularly on a newer site or a newer domain. Resubmitting the sitemap can nudge discovery along; it doesn't force indexing on any particular schedule.

Marketing and CRM in the Olmira admin

Where this shows up in Olmira

The dashboard-versus-live-version gap above is a real category of bug on many platforms, and it's one Olmira closes by design for page structure specifically: once a site is published, adding, renaming, deleting or reordering a page updates the live version automatically — there's no separate "republish" step to remember just to keep the page list itself correct. See how publishing works on the website builder page.

Publish something that stays reachable

Free 30-day trial. Cancel any time; your content stays yours.