Technical SEO
Why isn't my website appearing on Google? An indexing diagnosis guide
Short answer
A website not appearing on Google does not automatically mean it has a penalty. A new site may not be discovered yet, or a noindex tag, robots rule, wrong canonical, weak internal links, a server error or thin content may be blocking visibility. Diagnose each layer with Search Console.
Separate indexation from ranking
A URL can be indexed but not rank well for a target query. It can also remain undiscovered or excluded from Google’s index. Search Console’s URL Inspection is the primary source for establishing whether Google knows and indexes a particular page. Searching for a brand name is only a rough secondary check.
Check technical access
Confirm that the page opens consistently for people and crawlers. An HTTP 200 response, the correct canonical URL, no needless redirect chains and available mobile content are baseline checks. Accidental noindex decisions in robots files, meta tags or HTTP headers can hide important pages.
The XML sitemap should include only canonical URLs intended for indexing. A new or revised service page should receive contextual internal links from the homepage and related guides. Google’s crawling and indexing overview is a dependable primary resource for this diagnosis.
Review content and intent fit
A technically reachable page is not automatically useful enough to be indexed or competitive. It needs one clear purpose, a single H1, meaningful subheadings, genuine organisational information, current evidence and a relevant next step. Publish pages that answer a defined question thoroughly instead of repeating a phrase across thin text.
When similar pages compete, strengthen the most useful version and redirect outdated duplicates to the closest relevant destination. This creates a clearer information architecture for visitors and search systems.
Common indexation failures
During a redesign, a noindex instruction intended for staging is frequently carried into production. Incorrect canonical URLs, outdated sitemaps and restrictive robots rules can cause the same outcome. Verify these signals for the individual URL in Search Console; a functioning homepage is not evidence that every important page is indexable.
Redirects need the same care. An old guide or service URL should point to the closest useful replacement, not broadly to the homepage. Remove redirect chains and confirm the final destination returns HTTP 200. This protects both the visitor journey and the meaning of the legacy URL.
Another issue is relying on client-side JavaScript for essential content without checking the rendered result. Important headings, explanatory copy and page signals should be reliably available in the initial document where possible, and the mobile experience should be reviewed separately.
A practical check order
- Check the URL’s indexation state and stated reason in Search Console.
- Verify HTTP response, canonical tag, meta robots and redirects.
- Confirm that only the preferred URL is included in the XML sitemap.
- Add contextual internal links from relevant services and guides.
- Review whether the page answers a specific user need with current, original information.
This order prevents a minor technical block from being confused with a low-value content issue. Record the date of each fix and the signal you will evaluate afterwards. That provides a sound basis for interpreting subsequent visibility changes.
Decision tree: which symptom points to which cause?
The fastest way to diagnose is to stop running every check at once and start with one question: does Google currently hold this URL in its index? The URL Inspection result in Search Console answers that question directly and tells you which branch to follow.
The URL is on Google and the live test succeeds. There is no indexation block on this branch; the problem is query matching and competition. Identify the query where the page is missing, look at which page types appear in those results, and reposition the page if its intent does not match. Hunting for a noindex tag or a robots rule here only wastes time.
The URL is not on Google but the live test fetches the page successfully. Read the stated reason instead of guessing. Discovered – currently not indexed usually points to crawl priority and weak internal linking, while Crawled – currently not indexed points to a quality, duplication or intent assessment. Excluded by 'noindex' tag, Blocked by robots.txt, Duplicate without user-selected canonical and Soft 404 lead to tag, rule, canonical and template problems respectively.
The live test fails or returns an unexpected response. Drop the content discussion and return to infrastructure: server response code, redirect chain, authentication wall, regional blocking, and whether robots.txt itself is reachable. Improving copy cannot fix a page a crawler is unable to read.
When the tree ends you are left with a single hypothesis. Fix that one thing, record the date and repeat the same measurement; changing several variables at once makes it impossible to tell which fix actually worked.
What Search Console reports actually tell you
Search Console is not a penalty list; it is an instrument for observing how Google crawls and indexes your site. Reading the reports correctly is what separates a genuine blocker from noise.
The Page indexing report groups excluded URLs by reason. The total count is not a score by itself; the useful question is which bucket contains the URLs that matter to the business. Alternate page with proper canonical tag is usually evidence that your canonical choice is working rather than a failure. Counts also fluctuate naturally, so when a new reason appears, review the affected URL list first and then inspect one example in depth.
The Sitemaps report shows the gap between the URLs you submitted and the version Google read, along with the last read date and any parse errors. A sitemap is a discovery aid, not an indexing command, so being listed in it is not a guarantee of indexation.
URL Inspection separates the live test from the indexed version. The HTML you see in the live test is what Googlebot received at that moment, while the indexed copy may be older; a difference between the two usually means your latest change has not been processed yet.
Crawl stats break Googlebot requests down by response code and crawl purpose, which is where 5xx spikes and redirect growth surface early. Page experience field data, by contrast, can stay empty until enough traffic accumulates: an empty report means “no measurement yet”, not “no problem”.
It also helps to understand the limit of a request: asking Google to recrawl a URL places it in a queue, and it is not a promise of indexation or ranking. Report data is not real time either, so judge a fix across several measurement periods.
A realistic timeline after publishing
Visibility does not change at a single moment after a page goes live; it passes through consecutive stages. Google publishes no guaranteed duration for these stages, so it is more reliable to plan around stages and signals than around dates.
1. Discovery. Google has to learn that the URL exists. A sitemap entry, internal links from the homepage and related service pages, and genuine external links all accelerate this. A page that nothing links to may stay undiscovered for a long time even when it is listed in the sitemap.
2. Crawling. Googlebot divides its resources according to page value, update frequency and server response. Slow responses, needless redirects and large numbers of low-value URLs consume crawl budget and delay the crawl of the page you care about.
3. The indexing decision. Crawling is not indexing. At this stage Google assesses whether the content is original, sufficient and distinct from similar pages. Crawled – currently not indexed is produced here and is normally a content or duplication signal rather than a technical one.
4. Ranking. Entering the index is the starting point for visibility, not the finish. Competitive commercial queries depend on signals that accumulate over time, while longer and more specific queries can surface a page earlier.
5. Stability. Rankings fluctuate from day to day. Instead of reacting to a single day, repeat the same measurement at regular intervals and line the changes up against the dates of your fixes.
While you wait, the most productive work is usually to strengthen internal linking and content depth on the pages that already matter rather than publishing more pages. Launch quality also shapes how this timeline begins, which is why structure and technical foundations are worth planning together: see our corporate web design service.
What to do after a fix
After correcting a material technical issue or substantially improving a page, you may request recrawling in Search Console. That request does not guarantee immediate indexation or rankings; Google still needs to crawl and evaluate the page with other signals.
Track index coverage, crawl errors, priority-page traffic and qualified conversions together. If you are new to those reports, our Google Search Console essentials covers the ones worth checking regularly, and when the cause is thin or duplicated content, SEO copywriting explains what to fix. This turns search visibility into an improvement loop connected to business value. Explore our SEO, GEO and AEO service or contact Argo Ajans for an integrated review.
Frequently asked questions
Why is my website not showing up on Google at all?
Because Google has either not discovered the page yet or has chosen not to index it. The most common causes are a `noindex` tag, a robots.txt block, an incorrect canonical, redirect or server errors, and weak internal linking. Use URL Inspection in Search Console to establish the index state and the stated reason.
How long does it take to get indexed by Google?
Google publishes no guaranteed schedule for this. Discovery, crawling, the indexing decision and ranking are separate stages, and each moves at a different pace depending on site size, internal linking and server response. Track the stages and the signals you will measure rather than tracking a date.
What does crawled but not indexed mean?
It means Google read the page but did not judge it worth adding to the index. This usually signals thin or duplicated content, weak originality, or a page structure that does not match search intent. Deepen the page so it fully answers one question, and resolve competition between similar pages with canonicals and redirects.
Is requesting a recrawl after a fix enough?
No. A recrawl request only places the URL in a crawl queue; it guarantees neither indexation nor rankings. Google still recrawls the page and evaluates it alongside other signals. Make the request only after the technical fix is complete, record the date, and judge the effect across several measurement periods.