Skip to main content Scroll Top

Technical SEO: A Practical Guide for Small Businesses

Technical SEO: A Practical Small Business Guide

A practical guide to access, indexing and website performance | Reviewed 16 October 2026

Technical SEO is the work that helps search engines access, process and understand your website’s pages. It includes indexing controls, sitemaps, redirects, canonical URLs and the technical conditions affecting how people use the site.

Begin with important pages that should be publicly available. Check whether they load, whether Google can access their content and whether customers can complete the next step. Then investigate specific faults rather than trying to clear every warning in an audit tool.

You can carry out useful checks without being a developer. Changes to server settings, security rules, templates or site-wide indexing may need specialist help. This guide explains what to inspect, what the controls mean and how to verify a correction.

Use the wider SEO audit checklist for the full website review

Technical SEO

Start with eligibility rather than a perfect score

Google’s minimum technical requirements include an accessible page, a successful HTTP 200 response and indexable content. Meeting those requirements makes a page eligible for indexing; it does not guarantee indexing, a ranking or a customer visit.

A successful response alone is not enough. A blank template or an error message served with a 200 response may still fail to provide useful indexable content. Equally, an indexed page can remain unsuitable for a particular search.

Google’s technical requirements

Technical work supports content and business goals. A fast page with the wrong service information still needs editorial improvement. A clear service page behind an unintended access block needs a technical correction first.

On-page SEO for content and presentation checks

Choose a small set of pages to test

Include the homepage, an important service or category, a product or detailed guide and the main enquiry or booking route. Add a recently changed page if a problem began after an update. Test more than one template where the site uses different layouts.

Record each URL, its intended role and the symptom. “The enquiry page shows a challenge on mobile” is more useful than “the site has bad SEO”. Note when the fault began and any recent plugin, theme, hosting or security changes.

Priority Examples What to do first
Urgent Site unavailable, security warning or checkout failure. Contact the responsible host or specialist and establish the scope.
Important An intended search page is accidentally noindex or redirects incorrectly. Inspect the exact URL and confirm the setting causing it.
Investigate An audit warning, performance score or excluded URL without a clear impact. Check the page’s purpose before deciding that it needs a fix.

 

1 Check access and the response

Open the page while signed out, on a phone and a computer. Check the final URL, visible content, certificate warnings and essential functions. A normal browser visit does not prove a crawler receives the same response.

In Google Search Console, inspect the exact URL. The indexed result describes Google’s stored information; the live test checks current accessibility and processing. A successful live test does not mean that the page is indexed or will appear in results.

Use the available rendered output and resource information to investigate missing content. If a firewall, CDN or security plugin is involved, ask the person managing it to check relevant blocked requests and challenges. Confirm the responsible rule before changing it.

Search Console URL Inspection documentation

2 Separate crawling controls from indexing controls

Robots.txt gives supported crawlers instructions about which paths to crawl. It is not a password, and it is not a reliable way to remove a URL from Google Search. A blocked URL can still appear without its content being crawled.

A noindex rule tells supporting search engines not to index a resource. Google must be able to crawl the page to see that rule. Blocking the URL in robots.txt while relying on its noindex tag can therefore prevent Google from reading the instruction.

Control Purpose Important limit
robots.txt Manage crawling for crawlers that follow its rules. Does not protect private information or reliably remove a URL from search.
noindex Prevent indexing by search engines that support the rule. The crawler needs access to read the tag or response header.
Login or access control Restrict who can retrieve private content. Appropriate for private resources, rather than trying to hide them only with robots rules.

 

Google’s robots.txt introduction

Google’s noindex guidance

A WordPress check

If an important public page is unexpectedly excluded, inspect WordPress search visibility settings and the relevant SEO plugin’s page-level settings. Also check for a server or CDN response header. Change only an unintended restriction; private pages and testing sites need appropriate protection.

WordPress can serve a virtual robots.txt file. The public /robots.txt address may work even when no physical file appears in your host’s file manager. Establish whether WordPress, a plugin or the host controls the response before creating another version.

Do not use robots.txt to conceal hacked or malicious pages instead of removing the underlying problem. A security incident needs investigation and remediation.

Troubleshoot WordPress and Cloudflare crawler blocks

3 Check internal discovery and the sitemap

Important pages should be reachable through useful navigation or relevant internal links. A page that exists only in a sitemap can still be difficult for customers to discover. Use descriptive links to the intended destination.

An XML sitemap lists URLs you want search engines to know about. Keep it aligned with your preferred, publicly indexable pages. Avoid intentionally filling it with redirects, removed pages or pages you exclude from search.

WordPress or an SEO plugin may already generate the sitemap. Check the actual output before installing another generator. Submit the relevant sitemap in Search Console and inspect reported errors. Google says a sitemap helps discovery but does not guarantee crawling or indexing.

Google’s sitemap guidance

4 Understand redirects and genuine missing pages

A redirect sends a visitor or crawler to another address. Use a suitable permanent redirect when a page genuinely moves to a lasting replacement. Temporary moves have different requirements; choose the behaviour that reflects the change.

Check the starting and final URLs. Resolve loops and unnecessary chains, and update internal links to the correct destination. Do not redirect every removed URL to the homepage simply to make an error count disappear.

Response What it usually means Useful action
200 The request succeeded. Confirm the page actually contains the intended content.
301 or 308 A permanent redirect. Check that the destination is the appropriate replacement.
404 or 410 Content is not found or has been removed. Fix unintended broken links; retain a genuine removal when no suitable replacement exists.
5xx A server-side failure. Ask the host or developer to investigate, especially when repeated or widespread.

 

A 404 is not automatically a site-wide SEO fault. It can be the correct response for removed content. Prioritise errors affecting important pages and customer routes, then investigate the cause.

Google’s HTTP status code guidance

5 Treat canonical URLs as a preference signal

A canonical URL is the representative version of duplicate or very similar content. A rel=”canonical” annotation signals your preference to Google; it does not force Google to choose that URL.

Keep the preference consistent with internal links, sitemap entries and redirects. Inspect Google’s selected canonical in Search Console when an important page is unexpectedly treated as a duplicate. Check the content relationship and conflicting signals before editing the tag.

Do not point unrelated service pages at one another as a shortcut. Do not canonicalise every translated page to the English homepage. Different language versions need an appropriate international implementation, including hreflang where relevant.

Duplicate URLs do not automatically mean a penalty. The task is to understand which versions should remain available and how their signals should be handled. Get help with complex product filters or multi-language configurations.

Google’s canonical URL guidance

International SEO and localisation

6 Check mobile content and rendering

Google uses the mobile version of a site’s content for indexing and ranking. Make sure essential information, relevant images, links and metadata are available on mobile. A shorter layout should not remove the substance needed to understand the page.

Google can render JavaScript, but a script error or inaccessible resource can affect what it processes. Compare the visible page with the rendered output available in URL Inspection when something important is missing.

Test the mobile navigation, forms and checkout as a customer. Check readable text, clear labels and usable controls. Use a real device where possible; a desktop preview is useful but cannot reproduce every condition.

Google’s mobile-first indexing guidance

7 Investigate performance without breaking functions

Core Web Vitals measure aspects of loading, responsiveness and visual stability. They are not a single loading-time score.

Metric What it assesses Good threshold
LCP — Largest Contentful Paint When the main visible content is rendered. 2.5 seconds or less.
INP — Interaction to Next Paint Responsiveness to user interactions. 200 milliseconds or less.
CLS — Cumulative Layout Shift Unexpected visual movement. 0.1 or less.

 

The thresholds are assessed at the 75th percentile of page loads. Use real-user field data when available, alongside lab testing for diagnosis. PageSpeed Insights can show both; a lab run and a field assessment answer different questions. Some pages lack sufficient field data.

Web.dev’s Core Web Vitals guidance

Investigate the actual bottleneck: an oversized main image, slow response, heavy scripts or unstable elements. A CDN, caching or script optimisation may help a particular problem, but none is a universal fix. Good scores do not guarantee top rankings.

With WordPress, test changes to minification, delay, caching or image handling carefully. Confirm sliders, consent controls, forms and checkout still work. Save the previous setting, change one diagnosed area at a time and restore it if the change introduces a fault.

PageSpeed Insights

8 Check HTTPS and relevant structured data

Use working HTTPS for public pages, with a valid certificate and no browser security warnings. Ask the host to investigate certificate failures, mixed-content problems or inconsistent HTTP-to-HTTPS redirects. A padlock does not prove the site is free of malware.

Keep relevant structured data consistent with the visible page. Check what your theme or plugin already produces, then test the supported feature. Google’s Rich Results Test and Schema Markup Validator have different scopes.

Validation does not guarantee a rich result, ranking improvement or AI citation. Useful visible FAQs can remain without an expandable Google FAQ result. Structured data is not a requirement for every page to be indexed.

Google Rich Results Test

Schema Markup Validator

Schema markup explained

9 Distinguish AI search access from training choices

For Google AI features, established technical SEO remains relevant. Google documents indexing and snippet eligibility among its requirements, but an eligible page is not guaranteed selection. It does not require llms.txt or special AI schema to produce citations.

Provider controls differ. OpenAI uses OAI-SearchBot for ChatGPT search and GPTBot for content that may be used in model training. Their settings are independent: allowing search access does not require allowing GPTBot.

Avoid assuming every AI training restriction blocks Google or every bot can be managed through the same rule. Check the provider and the actual request. An accessible site still needs useful, accurate information.

Google’s generative AI search guidance

OpenAI’s crawler documentation

The detailed crawler-access troubleshooting guide

A simple WordPress investigation and retest

This example is fictional. A service page opens for an administrator, but a signed-out mobile visitor sees a security challenge. Search Console also reports a failed live test. The owner records the exact URL and test time.

The person managing security checks the request logs and identifies the relevant challenge rule. They retain the original configuration and make a targeted correction, rather than disabling protection across the whole site.

After any necessary cache clearing, they retest signed-out access and URL Inspection, inspect the content and submit the form. They check delivery and confirmation. If the correction causes another problem, they roll back and investigate again.

A successful retest shows that the immediate access problem has been addressed under those conditions. It does not prove the page is now indexed or that traffic will recover. The owner monitors subsequent indexing and performance separately.

Record the fix and its evidence

Before implementation, confirm a usable backup and who can restore it. For WordPress, recovery may require both files and the database. Retain configuration values separately when the change is outside WordPress.

WordPress backup guidance

Use a small log: affected URL or template, symptom, evidence, responsible person, change, rollback and retest result. Keep unresolved items visible rather than marking an entire audit complete because one test passed.

Retest representative pages after a relevant release or configuration change. Monitor Search Console messages and important customer functions. Set a review routine that fits the site’s complexity; a quarterly audit is not a substitute for acting on a verified urgent fault.

When traffic drops, compare affected pages and check demand, tracking and security as well as indexing. An algorithm update near the same date does not establish the cause, and technical fixes do not make a site immune to future changes.

Investigate a search traffic drop

What to do yourself and what to hand over

An owner can usually inspect pages, test customer journeys, review reports and document symptoms. Get appropriate help for server faults, persistent indexing conflicts, security incidents, complex redirects or migrations.

Give the specialist the exact URLs, test dates, relevant reports and recent changes. Agree who implements, who checks the result and how to restore the previous state. Automated audit tools can find issues to inspect, but do not reproduce Google’s systems or prove the cause of a ranking change.

Plan a manageable DIY SEO role

Sources and further reading

Guidance reviewed on 16 October 2026. Refer to current provider documentation before changing technical controls.

Google — Technical requirements

Google — URL Inspection

Google — Robots.txt

Google — Noindex

Google — Sitemaps

Google — HTTP responses

Google — Canonical URLs

Google — Mobile-first indexing

Web.dev — Core Web Vitals

Google — Generative AI search guidance

OpenAI — Crawlers

Secret Link