SEO

Technical SEO basics: how to spot problems that stop a website being found

Understand crawling, indexing and common technical checks without starting with an overwhelming audit report.

By Graphic Core   /   Published
Monthly guide series: April 2025

A laptop displaying illustrative charts next to a magnifying glass.

Start with discovery and access

A search engine has to discover a page, access its content and decide whether to include it in its index before that page can appear in ordinary search results. Technical SEO looks at whether the website makes those steps practical. It is one part of search visibility, alongside useful content, relevance and other factors.

Begin with the pages important to your business: your homepage, main services and essential contact information. Make a short list of their addresses. You do not need a hundred-page report to start asking whether those pages load correctly and can be reached through the site's navigation.

Check how pages are linked

Follow links from the homepage or main menu to each important service. A person and a search engine should be able to find the pages through ordinary links. If a service is only available after typing into a search box or clicking a control that does not expose a real link, ask your developer to inspect it.

Use descriptive links so visitors know where they lead. For example, a link labelled 'Website care' is more informative than several identical 'Click here' links. Avoid adding every page to the main menu; related links within relevant content can help keep navigation manageable.

Understand status codes and redirects

A page address can return different responses. A normal live page should be served successfully, while a permanent move should send visitors to the appropriate replacement. A genuinely removed page may return a not-found response. These signals do different jobs, so diagnose the situation before changing settings.

Check old addresses after a redesign. If a visitor searching for a particular service is sent to an unrelated homepage, they may struggle to continue. Keep a record of important address changes and ask your developer to map each one to the closest relevant destination where appropriate.

Review indexing instructions

Websites can include instructions that discourage indexing or restrict crawling. These settings are useful for private previews and certain non-public pages, but they need careful handling during launch. A page that should be publicly discoverable should not remain unintentionally marked noindex.

Robots rules and noindex directives serve different purposes; blocking crawling is not a substitute for a carefully planned indexing decision. Use Search Console and a developer's help to investigate an important page, and never assume that a change will appear in search results immediately.

Look at duplicate and preferred pages

Sometimes more than one address shows very similar content, for example because of tracking parameters, sorting or alternative URL formats. A canonical signal can indicate a preferred version, but it is not a guarantee that Google will choose it. Consistent internal links and sensible redirects also help reduce confusion.

Do not label every similar service page as a duplicate without checking its purpose. Two genuinely different services may deserve separate explanations, while several pages that merely swap a town name may not give visitors enough reason to use each one. Review content and technical signals together.

Prioritise by customer impact

A slow or awkward mobile page can make it harder for a visitor to find information or send an enquiry, even when it is technically indexable. Check the experience on a real phone and use performance tools as diagnostic aids. A single score should not replace testing the actual tasks customers need to complete.

Create a short action list: the issue, affected URLs, who will fix it and how you will verify the change. Start with broken enquiry routes and inaccessible key pages, then address wider improvements. Recheck after deployment and allow time for search engines to revisit the site.

A first investigation for a missing service page

Suppose your website care page is not appearing in a search you expected. First open the exact address in a normal browser, then follow a link to it from another page on the site. Check that the content describes the service and that a visitor can reach the contact route. Record the address and any unexpected redirect or error rather than immediately changing several settings.

Next inspect that URL in Search Console if you have access. If the page is unintentionally noindex or unavailable to Google, ask the responsible developer to identify why and verify the fix. If Google can access and index it, the next question may be whether the page answers the search and offers distinct value. Search visibility involves more than the absence of technical errors, and no single check guarantees a particular result.

What to ask a technical specialist

Ask which important URLs are affected, how a problem was identified, how it affects visitors or search access, and what evidence will show that the proposed fix worked. Request a priority order rather than a list of hundreds of unexplained warnings. Agree who will make the change, whether testing is needed and how you will check the result after deployment. Technical recommendations should connect to a real issue; a tool labelling something a warning does not by itself establish that it is important for your business.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION