Only your homepage shows up on Google? What that can mean and how to fix it

You typed site:yourdomain.com into Google and got one result: the homepage. Here's the ten-second check I run, what that pattern can point to, what Search Console's "crawled, not indexed" actually says, and the design fixes that matter more than another sitemap submit.

Overhead view of a white desk with an open notebook, smartphone, glasses and the edge of a laptop, ready for a site: search check

A few days ago someone asked Google's John Mueller on Bluesky about a site that used to have pages indexed and now only shows the homepage. Mueller wrote, as reported on 3 November, that off-hand it "sounds like a general quality issue" that might be unrelated to an older hack, and that timing with a core update can make the drop hard to spot. That is one comment about one case. It is not a diagnosis of your site, and it is not a penalty notice. But if your own site: search has collapsed to a single URL, it is a good day to stop guessing and look.

Do the site: search today

Open a private window and search site:yourdomain.com, with your real domain and no space after the colon. Count what comes back.

  • Nothing at all: Google has not indexed the site, or not yet. Start with the checklist in why your site isn't showing in Google: robots.txt, noindex, Search Console.
  • Dozens of URLs, including services and articles: you are fine on discovery. Move on.
  • Only the homepage, or the homepage plus a couple of old pages: that is the pattern this piece is about.

Do the same search on your phone. Then open Google Search Console, pick the Domain property, and open Page indexing. Write down how many URLs are indexed versus not indexed, and which reasons dominate the "Why pages aren't indexed" table. The site: result is a public snapshot. Search Console is the ledger behind it.

One more pass if you publish in two languages: search each host or path you care about. A site can look healthy in English and thin in the other language, or the other way around.

Why Google skips pages: thin, duplicate, orphaned, slow

Google has to choose. It crawls far more URLs than it keeps. When pages fall out, or never get in, the usual causes I see on client sites are boring:

Thin. A "Services" page with three adjectives and a contact button. A city page that repeats the homepage with the town name swapped. Google already has thousands of pages that say the same thing better.

Duplicate. HTTP and HTTPS both live. www and non-www both live. A printer-friendly copy, a staging subdomain that got linked, or product filters that create near-identical URLs. One version should be the canonical; the rest should redirect or stay out of the sitemap.

Orphaned. The page exists, the sitemap lists it, and nothing in the menu, footer or body links to it. If people can't click to it in two or three steps from the homepage, Google can treat it as unimportant. I still find service pages that only appear in a PDF price list.

Slow or empty above the fold. The first screen is a hero animation and a slogan; the real text loads later, or only after JavaScript. Visitors bounce. Crawlers that do render the page still have to decide whether the content was worth the wait. Speed and clear text on first paint are web design problems before they are SEO tricks.

None of these is a secret ranking lever. They are the difference between a site someone can use and a shell that looks finished in the browser preview.

What Search Console's "crawled, not indexed" actually means

In the Page indexing report, Crawled - currently not indexed means Google fetched the URL and chose not to add it to the index. On 3 November, search-marketing press reported that Google had rewritten that help text. The live Page indexing report now says, in short, that Google crawled the page but did not index it; that Google does not index every page on the web; that the message is common; and that it does not necessarily need action. For important pages, use URL Inspection and other tools to check for blocks. The report-an-indexing-issue form is for when you have already diagnosed the site and suspect a complete, site-wide indexing bug, not for every lonely URL.

So the status is a decision, not a server error. Resubmitting the same thin page ten times rarely changes it. Rewriting the page, linking to it from the menu, and making sure the content is visible without a special click does more.

We have one of these on our own Bulgarian side right now. /bg/statii/google-biznes-profil/ was crawled on 3 November and is still marked crawled, not indexed. The English twin is fine. That is a content and usefulness call on Google's side, not a missing sitemap entry.

Fixes that are really design fixes

Most of the work that moves the needle here is ordinary site work.

Give each real service its own page. Not a scrolling homepage with six H2s. Write a page that states the offer, who it is for, what you actually deliver, a rough timing or scope, and the questions people already ask on the phone, because that is the copy Google and a hurried visitor both need in one place. Prices help when you can share them. If you only have one "Services" URL, split out the two or three offers that actually earn money first.

Put those pages in the main menu. A link in a blog post is nice. A link in the header is a vote. Drop-downs are fine; pages that exist only in the sitemap are not.

Write real copy above the fold. A visitor on a phone should see what you do and how to contact you without scrolling past a full-screen video. The same text is what Google evaluates first.

Keep one clear URL for each idea. Pick HTTPS, pick www or not, redirect the rest, and match the sitemap to the live redirects. Website maintenance is where broken redirects and forgotten staging links hide.

Seasonal pages need a home before the rush. A Black Friday landing page that goes live with no menu link and thin text is a classic crawled-not-indexed candidate. The timing notes are in when your Black Friday page should go live.

If the template itself buries the content, fights mobile layout, or takes forever to become useful, that is a redesign conversation, not another meta-tag pass. SEO still matters for Search Console, sitemaps and the boring technical checks; it does not replace pages worth indexing.

What we did on our own site this week

I only quote our numbers from Search Console. Earlier this week we were at 73 of 78 sitemap URLs indexed. After fixing discovery issues, requesting indexing for several new pairs and resubmitting the sitemap, we reached 79 of 80 on 4 November. As of the 5 November check we sit at 79 of 82: the two newest URLs are live in the sitemap but still unknown to Google, and that one Bulgarian guide is still crawled, not indexed. No indexed page dropped out.

What actually moved: clearer internal links to the pages we care about, Request indexing for URLs Google had not discovered, and not treating "crawled, not indexed" as a button problem. What did not: inventing more pages for the sake of the sitemap.

When do you rebuild?

Stay with the current site if the structure is sound, the menu already lists the real offers, and you mainly need fuller text, redirects and Search Console hygiene. That is days or a couple of weeks of focused work.

Consider a rebuild when the CMS fights every new page, when important content only exists inside tabs or scripts, when mobile layout collapses the offer, or when you have been polishing the same thin template for months and the index still will not grow. At that point you are paying for maintenance on a shape that cannot hold the content you need.

If you want a second pair of eyes, email the site: screenshot and your Search Console Page indexing summary to contact@magnuszgr.com. I will tell you whether I would rewrite, relink or rebuild, and I will not invent a ranking promise either way.

One homepage in Google is a signal to look harder at the rest of the site. It is not a verdict. Fix the pages people should find, link them like you mean it, and give Google something worth keeping.

Read next