A focused diagnosis. A usable handoff.

Technical SEO Audit Services

Know what is broken, what matters, and what to fix next.

  • AllScale. An October 2026 production browser retest followed a 301 to a 200 response and found 10 articles at the intended Webflow destination.
  • Expertise URL migration. An October 2026 audit verified single-step 308 redirects on 3 former language routes, alongside a review of generated URLs and 7 child sitemaps.

For teams investigating indexing, rendering, redirects, or a growing technical backlog. Get findings with evidence, priorities, and acceptance criteria your developers can use.

The work, brought to life

From a technical finding to a clear next action.

Explore the research, delivery, and decisions behind this service.

Service workflow · Illustrative interfaces

Inside the workflow · 04

Make the priorities actionable.

Connect impact, dependencies, and acceptance conditions.

Explore the workflow

From our own website · September 2026

One finding, all the way to verification.

See how we unified the language URLs on Meridian’s own website: the original behavior, the developer task, and the checks used to verify the change.

MER-01 / Language URL consistency

Implemented · retested

Observed → changed

Before: language selected by a query parameter

/services/seo-services?lang=zh

After: a dedicated Chinese URL

/zh/services/seo-services

Legacy request → 308 redirect → Chinese page with matching canonical and language alternates.

View the service page
Evidence
The previous service links used ?lang=zh. The site’s locale handling and page metadata needed one consistent URL rule.
Why prioritize it
Language routing is shared across service templates. A shared rule keeps navigation, canonical targets, and alternates aligned.
Implementation owner
Website developer: add permanent legacy redirects, localize internal links, and update page-level language signals.
Acceptance
Check the response chain, final language, self-canonical, reciprocal alternates, and both language-switch directions.
Download the finding and retest checklist

Rendering, URL rules and a developer handoff

Check the response, the rendered page and the destination.

A technical audit connects the exact URL, returned HTML, browser behavior and intended content. The AllScale record below shows how that comparison becomes a specific implementation task and a dated retest.

AllScale · Webflow blog · October 13–15, 2026

Three pagination parameters. One destination to verify.

An AllScale blog URL combined pagination parameters from three lists. We traced the selected category and its articles, compared response versions, and specified an exact redirect to the matching page.

Original combined URL
/blog?6f1ab5ce_page=2&bb481863_page=10&f94dbc80_page=3
Matching destination
/blog?f94dbc80_page=3
  1. 01 · October 13 · Diagnose

    Compare output and content

    An HTTP sample declared /blog as canonical; the browser recorded the full combined URL. We compared the selected list and response versions to determine the intended page.

  2. 02 · October 14 · Implement

    Keep the matching page

    The selected content matched Stable Scoop page 3. One exact Webflow 301 rule was saved for the old combination. Staging returned 301 → 200, with a self-referencing canonical on the destination.

  3. 03 · October 15 · Browser retest

    Check the same navigation

    A production browser navigation followed 301 → 200 to the single-parameter URL. The captured response HTML and rendered canonical matched; Stable Scoop page 3 displayed 10 articles.

SEO decision
Match each pagination URL to its actual content. Preserve the distinct page and its self-referencing canonical, then give the obsolete combination one defined destination.
Developer handoff
SEO supplies the source URL, destination, content comparison and acceptance checks. The site maintainer configures the exact redirect; SEO retests the response chain, canonical and pagination.
Follow-up check · October 15
A separate HTTP request still received the old URL as 200 with /blog canonical. Cache and request-version checks remain open alongside the successful browser retest.
Meridian website: a baseline rendering check

Our English and Chinese B2B pages were checked in a local production build on October 12, 2026. The service heading, consulting explanation and key links appear in both the delivered HTML and the rendered page.

Initial HTML
Request the page directly. Inspect the main heading, service description, index directives, canonical, and ordinary links.
Rendered page
Open the same URL. Compare the main content, expand the deliverables, and click the pricing and team links.
Decision and owner
Retain the server-delivered content and working links. The developer owns shared template behavior; the editor owns service wording. Retest both language versions after a change.

Recorded checks · English and Chinese B2B pages

Main service heading
The B2B SEO H1 is present in initial HTML and in the rendered page.
Consulting explanation
The service description and customer implementation responsibilities appear in both versions.
Pricing and team links
Ordinary links are present in initial HTML; clicking them opens the intended guide and team section.
Deliverable disclosure
The summary is available on load; the browser expands the complete package details.
Inspect the B2B page used in the check Download the rendering check record

Scope follows the website

Check the systems behind your pages.

We agree on markets, templates, environments, and URL samples before the audit. Large sites need a sampling plan and explicit exclusions.

Discovery & access

Internal paths, orphan candidates, sitemaps, status codes, robots rules, and server availability. Search Console and logs add context when available.

Indexing & URL rules

Index directives, duplicates, canonical choices, redirects, parameters, and language alternates.

Rendering & templates

Compare delivered HTML and rendered content. Review navigation, key links, structured data, and representative page types.

Performance & release risk

Investigate loading and interaction problems using available field and lab data. Identify changes that need a developer or wider release plan.

Audit priority planning example

Fix the constraint, not the longest issue list.

Priority combines page value, affected scope, confidence in the diagnosis, and implementation effort. These examples show the reasoning; your order depends on the evidence.

  1. 01Investigate immediately

    An important product template unexpectedly returns noindex.

    Confirm intent and deployment scope first. A shared directive can affect every page using the template.

  2. 02Investigate before scaling

    Parameter URLs multiply while important pages wait to be crawled.

    Check logs, discovery paths, and URL value before attributing the delay to crawl capacity.

  3. 03Schedule with related work

    A secondary page has a long title but remains accessible and relevant.

    Improve the title in its content review. Assign the title update to the content review queue.

From investigation to handover

A report your team can act on.

The audit scope includes diagnosis, prioritized findings, recommended tasks, and a handover discussion. Code changes, content production, and post-release support are agreed separately.

Crawled but not indexed, with an internal developer

Bring representative URLs, their templates, and dated Search Console results. We compare canonical versions, HTTP and indexing directives, initial HTML and rendered content, then page purpose and internal links. Your developer receives the observed finding, change specification, owner, and retest steps; your editor takes the content tasks.

Follow the three-check indexing workflow
  1. 01Agree on the baseline

    You provide the site, symptoms, recent changes, and available access. We define page groups and evidence gaps.

  2. 02Investigate and document

    We inspect representative URLs and shared rules, then record findings and the confidence behind each recommendation.

  3. 03Hand off the work

    You receive an issue register, a priority queue, developer-ready records, and scope limitations. Together we confirm owners.

  4. 04Retest agreed changes

    Agree on the retest window and page samples. Verify the implemented change separately from Google’s later crawl or indexing decision.

Before we start

Define the scope before the quote.

Template count, URL volume, languages, JavaScript behavior, data access, and implementation support change the work. Share your website and main symptoms first; the proposal sets the fee, delivery date, exclusions, and review window.

Compare SEO audit costs and scope
Can a crawler export replace this audit?

A crawl supplies observations. The audit adds context, validation, priorities, ownership, and a way to verify the recommended changes.

Do you need Search Console or server logs?

Public checks can start without them. Some conclusions require access; the report states what was checked, what is inferred, and what remains unknown.

Is implementation included?

The audit provides diagnosis and an actionable handoff. Your developers implement unless an implementation scope is explicitly agreed. Ongoing support belongs in a separate service scope.

Will every page get indexed?

No. We can verify technical changes and investigate remaining barriers. Google’s crawl, indexing, and ranking decisions are separate outcomes.

Choose your next step

Bring the website and the problem.

The first conversation clarifies the investigation and available evidence. The proposal defines the detailed audit scope and delivery date.

Related services

Keep Exploring SEO Services

Explore adjacent capabilities in the same service family, or return to the parent page for the complete program.

View all SEO Services
SEO for B2B
Connect buyer research and evaluation to qualified sales conversations.
SEO for B2C
Help consumers discover, compare, and buy your products or services.
SEO for SaaS
Build acquisition around signup, activation, paid conversion, or demos.
SEO Methodology
Review the workflow, implementation example, and measurement responsibilities.
On-page SEO
Improve page targeting, content signals, and internal linking for priority URLs.
Technical SEO
Resolve crawl, indexing, rendering, performance, and site architecture issues.
SEO Content Writing
Read complete writing samples and compare research, editing, and delivery scope.
International SEO
Connect market research, local pages, language review, and inquiry paths.
National SEO
Build a nationwide search program across strategy, technical foundations, pages, content, and authority.
White-label SEO & GEO
Add specialist SEO and GEO delivery behind your agency or consultancy brand.
SEO Migration
Plan URL changes, coordinate launch checks, and review the site after a move.
Programmatic SEO
Scale high-intent landing pages with structured, reusable templates.
Link Building
Earn relevant authority through editorial outreach, digital PR, and linkable assets.
Keyword Research
Map search intent, topic clusters, and priority keywords to the right pages.