Technical diagnosis, WordPress troubleshooting and practical implementation
Technical SEO Nottingham for WordPress and Small Business Websites
Find the fault before paying for more activity
Find the technical problems affecting your website — and fix the ones that matter
Technical SEO in Nottingham helps businesses investigate pages that are not indexed, broken redirects, competing URLs and page-builder faults. We identify issues affecting important pages, correct them within the agreed scope and check the result.
For a small service business, the problem is rarely a shortage of technical reports. It is working out which issues actually affect commercially important pages, correcting them safely, and checking the site now produces the intended result.
We investigate crawling, indexing, canonical signals, redirects, architecture, structured data and WordPress configuration — and within the agreed scope, we make the corrections.
Where crawlability, canonicals or store-locator rendering affect a genuine location network, Multi-Location SEO coordinates the branch-level structure and governance.
Recognise the symptoms
Does your website have a technical SEO problem?
- Important service pages are not appearing in Google
- Search Console shows pages crawled but not indexed — see what indexing reasons mean
- Rankings or enquiries fell after a redesign or migration — see what to check after a redesign
- Google chose a different canonical URL from the one intended
- Old URLs redirect through several hops or return errors
- Rank Math or Yoast looks healthy while visibility stays weak
- The site is slow despite a caching plugin
- Elementor or Divi is producing inconsistent headings and layouts
- Staging, archive, attachment or parameter URLs are reachable
- Two plugins output contradictory structured data
- An automated audit produced hundreds of warnings and no priorities
These have different causes. A page can be discovered without being crawled, crawled without being indexed, and indexed without ranking. A site can pass every automated test while its templates and plugins send contradictory signals.
The first job is establishing which situation applies.
Remove barriers, not context
What technical SEO actually does
It removes obstacles that stop search engines and visitors using a website properly.
That means checking whether important pages can be found, whether crawlers may access them, whether the right URLs can be indexed, whether redirects lead somewhere relevant, whether canonicals identify the preferred page, whether internal links show what matters, whether structured data matches what is visible, and whether a migration preserved the signals it should have.
Indexing is not ranking, and ranking is not the same as generating enquiries.
Most small businesses are not running enormous international sites. They run WordPress, a commercial theme, a handful of plugins and a page builder. That changes what a useful technical service should look for — and it is where generic audits tend to stop.
Understand the build
Why page-builder websites break differently
Page builders enable sophisticated layouts without custom templates, but they also introduce fault patterns that are hard to see inside the visual editor.
Loaded assets
Code travels further than the widget
A theme or builder may load CSS, JavaScript, fonts and widget files across pages that use none of them. Adding another optimisation plugin does not remove the underlying dependency; it adds another configuration layer that must be tested.
Document structure
Visual hierarchy can replace heading hierarchy
A heading may be chosen because it is the right size rather than the right level. The page looks correct while its document structure contains repeated H1 elements, skipped levels or sections without meaningful headings.
Responsive layouts
Hidden duplication remains in the HTML
Desktop, tablet and mobile versions are sometimes built as separate containers. Content can be delivered more than once, but its effect on crawlers and screen readers depends on how each version is hidden. Check the rendered output and accessibility tree before deciding whether a change is needed.
Global templates
One mistake can spread across every page
A faulty header, footer, archive template or reusable section affects every URL using it. Fixing each page manually is the wrong answer when one shared template creates the fault.
Rendered output
The editor is not the page a crawler receives
Caching, conditional templates, optimisation plugins and device rules change the final output. Technical checks have to inspect the live rendered site, not only the dashboard.
Overlapping controls
Correct settings can still conflict
Astra, Elementor, Rank Math, caching and schema plugins can influence the same page. Each may look correct in isolation while their combined output contains duplicates or contradictions.
Investigation follows the problem
Technical SEO services in Nottingham: what we check
Access
Crawling and indexability
Meta robots, X-Robots-Tag headers, robots.txt, sitemaps, status codes, internal discovery, orphaned pages and staging protection, read against Search Console indexing data. A sitemap supports discovery; it does not compel inclusion. Our guide to Search Console indexing statuses explains what the reported reasons mean before you choose a fix.
Consolidation
Canonicals and duplicate URLs
Wrong self-referencing canonicals, canonicals pointing at unrelated pages, protocol and trailing-slash variants, parameters, WordPress attachments, taxonomy duplication, and conflicts between canonicals, redirects and sitemaps. Deciding whether genuinely overlapping pages should be differentiated, merged or left alone belongs under content consolidation and competing pages.
Journeys
Redirects and architecture
Broken links, chains, loops, deleted pages and migration maps, plus navigation depth, internal anchors and routes into commercial pages. A deleted URL should not default to the homepage; its replacement must be relevant.
Experience
Performance
Server response, images, script and style bloat, caching, theme and plugin overhead, layout shift, interaction delay and third-party services. Core Web Vitals and general speed are related but not identical.
Meaning
Structured data
Whether markup describes the visible page, business details stay consistent, plugins produce duplicates, unsupported ratings are marked up, prices match, and the final output still validates after implementation.
Controls are not judgement
What WordPress SEO plugins cannot decide for you
Rank Math and Yoast give you useful controls. Their scores are not an assessment of the website.
To check the basics yourself first, work through our WordPress SEO checklist.
A plugin can confirm a page contains a focus phrase. It cannot tell you whether another page targets the same intent, whether the URL belongs in the architecture, whether a canonical points somewhere sensible, whether a global template duplicates its schema, whether a service warrants its own page, or whether the visible content supports the markup.
Validation is only one test
Structured data can validate and still achieve nothing
Passing a validation test confirms the markup follows the tested format. It confirms nothing else.
FAQ markup
A valid type without a Google rich result
Google’s Search Central changelog records that FAQ rich results stopped appearing on 7 May 2026, followed by removal of related testing and reporting support. A plugin may still report the Schema.org markup as valid, but Google no longer displays that feature.
Review stars
A business cannot award itself stars
Where an organisation controls reviews about itself, pages using Organisation or LocalBusiness markup are ineligible for Google’s review-star feature, including reviews displayed through a controlled third-party widget.
AI features
Schema is not an AI shortcut
Google says no special structured data is required for AI Overviews or AI Mode. Markup can make visible information easier to interpret; it cannot substitute for the answer being on the page.
You do not usually need to remove accurate FAQ markup merely because the Google feature has gone. Structured data should improve clarity, not manufacture a feature the page cannot legitimately receive. See Google’s Search Central documentation changelog, review snippet guidance and AI features guidance.
A diagnostic order that protects the important pages
How we work through a technical problem
How findings are prioritised
Not every warning deserves development time
| Priority | Meaning | Example |
|---|---|---|
| Critical | Prevents important content being accessed or indexed | An unintended site-wide noindex |
| High | Materially affects consolidation or key journeys | Canonicals pointing service pages elsewhere |
| Medium | Weakens discovery or adds friction | Important pages buried in the architecture |
| Low | Maintenance or refinement | Minor markup cleanup |
The local pattern
What breaks on small business websites around Nottingham
The local small-business web follows a pattern. A site is built once, by an agency or a freelancer, and handed over. Then it is edited for years by the owner: a plugin added for a form, a page duplicated to save time, a theme updated, a redesign commissioned from someone else who never saw the original URLs.
Nothing in that is careless. It is what running a business looks like. But it produces a particular kind of damage—duplicated pages competing with each other, staging settings left switched on after launch, old addresses that stopped working when the site was rebuilt, and tracking that quietly stopped recording months before anyone noticed.
Hosting can affect how quickly a page starts to load. On some shared plans, server response may be slow; image compression alone will not resolve a slow server response. Measure the actual cause before choosing a fix.
The two faults below came out of exactly this pattern.
Two faults we have dealt with
Competing markup
Duplicate Service schema from two systems
A service page was emitting one Service entity through Rank Math and a second through hand-inserted JSON-LD. Both validated independently, but maintaining two meant the name, description and price could drift apart. We removed the handwritten duplicate, kept the managed entity and checked the live source to confirm a single Service node remained.
Consistency across the site
A phone number changed in one place but not the others
Correcting a telephone number meant visible copy, clickable tel: links, header and footer elements, and structured data. Changing what visitors could see was the easy part. Every technical reference had to be checked so that people, browsers and search systems all received the same number.
These are small examples, but they are why technical SEO is not solved by exporting a list of warnings. The work is understanding the site’s actual state, changing it safely and confirming the output.
From finding to correction
Do you implement, or just advise?
We implement where the platform, access and agreed scope allow.
| Investigation | Implementation |
|---|---|
| Identifies and prioritises the fault | Applies the approved correction |
| Records affected URLs and templates | Changes configuration, code or content |
| Establishes a baseline | Includes QA and recrawling |
| Can brief your developer | Needs suitable site access |
If your existing developer controls the site, we can supply the evidence and work alongside them.
Controlled access
What access is needed?
Depending on the problem: read-only Search Console, analytics, WordPress administrator or staging access, hosting or CDN details, and sometimes server logs. We ask only for what the agreed work requires.
Material changes are approved and recorded, a backup is available before risky implementation, and significant changes are tested on staging where practical. Passwords are not sent by ordinary email, role-limited accounts are preferable, and temporary access is removed when the project ends.
Protect the signals already earned
Redesigns and migrations
Migration work reduces avoidable risk and makes unexpected changes easier to diagnose.
It can cover recording existing URLs, mapping redirects, checking staging protection, canonicals and sitemaps, updating internal links, testing key templates, inspecting the site after launch, and monitoring Search Console for pages lost in the move.
No provider can guarantee that a migration preserves every ranking or avoids every fluctuation.
Clear starting points
What technical SEO costs
| Detail | Defined technical correction | SEO audit with implementation |
|---|---|---|
| Price | From £350 | £695 one-off |
| For | A fault already identified, with controlled scope | An unclear cause or several problems at once |
| Includes | Investigation of the fault, the fix, QA and a recrawl | Full investigation, prioritised findings and agreed corrections |
| Excludes | New page creation and redesign work | Large, custom, multilingual or complex migration projects |
| Typical turnaround | Within a week of access being granted | Two to three weeks |
| You provide | Site access and a description of the problem | Site access plus read-only Search Console |
The £350 figure depends on the platform, affected templates or URLs, available access, testing required and whether another provider is involved. Scope, exclusions, access and responsibility for implementation are confirmed before paid work begins.
Honest limits
What technical SEO cannot promise
- That Google will crawl or index every eligible page
- A particular ranking after a correction
- Recovery by a fixed date
- A perfect PageSpeed score
- That every platform limitation can be changed
- That a migration causes no fluctuation
- A rich result because markup validates
Google controls crawling, indexing and result selection. Hosting, themes, plugins, third-party scripts and platform restrictions limit what is achievable.
What we do is identify the evidence, separate meaningful faults from low-value warnings, implement what is agreed, and confirm whether the technical output changed as intended.
Straight answers before you enquire
Frequently asked questions
Why is Google not indexing my page?
noindex directive, canonical conflict, discovery problem, duplication, rendering issue, or Google choosing not to index it. The URL needs investigating before a cause can be named.Can technical SEO improve rankings?
Should I remove FAQ schema now the rich result is gone?
FAQPage remains a Schema.org type. Remove it where it no longer describes visible questions, not simply because Google no longer displays the feature.Can you investigate Elementor, Divi or Astra problems?
How long does it take?
How do you know whether a fix worked?
Do I need a full audit?
A useful first look
The free review
A preliminary look at the site and the problem you describe: obvious indexing restrictions, broken commercial pages, canonical or redirect concerns, visible WordPress configuration problems, and whether a defined fix or paid investigation is the sensible next step.
It is not a full crawl, complete technical audit, migration plan, guaranteed diagnosis or free implementation.
What to send
Four details help us start
- Your website address
- The main problem
- Which pages are affected
- Roughly when it started
Technical investigation or a defined correction?
An investigation is useful when the cause is unclear or several symptoms overlap. A defined correction suits an identified problem with an agreed scope; either route should include checks after implementation.
Indexing eligibility and search rankings
Fixing an unintended noindex or broken redirect can remove a technical barrier. It does not guarantee that Google will index a page or improve its rankings: relevance and competition matter too.
What to prepare before requesting help
Record the affected URLs, what changed and when. If available, provide read-only Search Console access and details of your website platform. Access and any paid work should be agreed before changes begin.
The next sensible step
Make your next decision on evidence
Tell us which pages are affected, what changed and when it began. We will say whether the next step is a defined correction, technical audit, migration support, working with your developer — or no paid technical work at all.
hello@seoagencyinnottingham.co.uk
Last reviewed: 23 September 2026 by David, founder.