Why your website does not show up on Google: 7 common technical errors

A website fails to show up on Google for three technical reasons: Google cannot crawl it (robots.txt, server, links), cannot index it (noindex, canonicals, sitemap) or does not understand what it is or who it is for (structured data, thin content, inconsistent company details). Slow mobile loading and the lack of a page per service make the problem worse. All of these faults can be detected in 15 minutes with Search Console, PageSpeed Insights and the page source code.

When a website does not show up on Google, the usual reaction is to assume it lacks content or that competitors have more authority. Sometimes that is true. Often the problem is a technical fault that is quicker to fix. This is the list of checks worth doing first. None of them needs paid tools.

Google works in three stages: it crawls, it indexes and it ranks. If one of the first two fails, the third never happens. Errors 1 to 4 belong to the first two stages; errors 5 to 7 to the third.

1. robots.txt blocks resources Google needs

The robots.txt file tells crawlers which parts of the site they may visit. A frequent error, especially on WordPress, is blocking folders such as /wp-content/ or /wp-includes/. That is where the images, CSS and JavaScript live.

If Google cannot load those resources, it renders the page without styles, may decide it is not mobile-friendly and does not index your images. Another typical fault is a Disallow: / inherited from the staging environment that blocks the whole site. The file should also declare the sitemap address with a Sitemap: line.

Important: robots.txt prevents crawling, not indexing. A blocked URL can appear on Google without a description if other sites link to it. To remove a page from the results, the right tool is noindex, and for Google to read it, the page must not be blocked in robots.txt.

2. Important pages marked as noindex

The tag <meta name="robots" content="noindex">, or its equivalent in the X-Robots-Tag HTTP header, asks Google not to show a page in the results. It is useful for pages such as "thanks for your message", internal search results or private areas. But it is often switched on by mistake: by inheriting a setting from the staging environment, by ticking the "discourage search engines" box in WordPress, or through an SEO plugin rule that applies noindex to a whole content type.

A services page with noindex cannot rank, no matter how prominently it sits in the main menu.

3. Sitemap missing, incomplete or contradictory

The XML sitemap is the list of pages you want Google to know about. If it has six URLs and your website should have sixty, or it includes pages that should not be indexed, Google gets a distorted picture of your site. The most confusing case is a sitemap that includes pages with noindex: you are saying "index this" and "do not index this" at the same time.

A correct sitemap includes only indexable, canonical pages, returns a 200 status code and has at most 50,000 URLs and 50 MB (if there are more, it is split with an index). It must be submitted in Search Console and declared in robots.txt.

4. Incorrect structured data

Structured data is code in JSON-LD format, using the schema.org vocabulary, that tells search engines and AI assistants who you are: organisation name, logo, address, phone number, opening hours, social profiles. Many plugins generate it from system data without anyone reviewing it.

A case I see often: the organisation appears with the name of the WordPress admin user ("admin" or the first name of whoever installed it) instead of the company name, or the logo points to an image that no longer exists. Search engines cannot identify you properly and local SEO suffers. For a business with physical premises, the right type is usually LocalBusiness or one of its subtypes, not plain Organization.

5. Poor speed on mobile

Most searches happen on mobile, and Google evaluates page experience with the Core Web Vitals. They are measured with data from real users, and a page passes when 75% of visits fall within the "good" threshold:

The most common cause of a slow LCP is a heavy hero image, in an old format and without declared dimensions. Compress it, convert it to WebP or AVIF, declare width and height and do not lazy-load it: the hero image should carry fetchpriority="high", not loading="lazy". A high INP usually comes from third-party scripts (chat, analytics, advertising pixels) that block the main thread.

6. Thin content and no page per service

A website with a single "Services" page listing five things competes poorly against one that has a page per service, with its own copy, FAQs, examples and indicative prices. Google indexes pages, not companies: if a service does not have its own URL, it cannot rank for that search.

Each service, material or customer type deserves its own page, designed to answer a specific search. It is also the kind of content AI assistants can cite as a source: a paragraph that defines the service, a list of what it includes and a direct answer to the usual questions. Google's helpful content guidelines insist on the same: written for people, with first-hand experience, and resolving the search intent.

7. Inconsistent company name and details

If your company appears as "Company", "COMPANY" and "Company Ltd" across the website, the Google Business Profile and social networks, search engines and AI take longer to recognise it as a single entity. Unify the name, address and phone number everywhere, including the structured data from point 4 and the footer.

What is not a technical error

Three situations that get mistaken for technical faults and are not:

• The website is new. Google can take days or weeks to crawl and index a newly published domain. Submitting the sitemap and requesting indexing of the key pages speeds things up, but does not make it instant.
• You search for your own brand and do not appear. If the company name is a common word ("Solutions", "Innova"), you are competing with thousands of pages. Check with site:yourdomain.com whether Google has your pages indexed; that separates the technical problem from the ranking problem.
• You appear, but on page three. That is no longer indexing: it is competition, content and links. The technical side is solved and the next phase begins.

How to do the review in 15 minutes

1. Search site:yourdomain.com on Google. If nothing comes up, the problem is in points 1 to 3.
2. Open /robots.txt and /sitemap.xml and review the points above.
3. In Search Console, look at the Pages report and the exclusion reasons. Inspect the URL of the home page and of one service page.
4. Run your home page through PageSpeed Insights, on mobile.
5. Review the structured data with the Rich Results Test.
6. Check that each service has its own indexable page and that the company name is identical everywhere.

One important detail: a high SEO score in Lighthouse does not mean everything is fine. That audit only checks basic aspects of a page and does not detect, for example, a robots.txt that blocks images, a key page set to noindex or a contradictory sitemap.

Technical first, then content, and investment last. Doing it in another order usually costs more.

If you want me to review your website, the web development service includes an initial technical audit with a prioritised list of fixes. And if you are also deciding which technology to rebuild it with, WordPress or custom website: how to decide may help.