A focused diagnosis. A usable handoff.
Technical SEO Audit Services
Know what is broken, what matters, and what to fix next.
For teams investigating indexing, rendering, redirects, or a growing technical backlog. Get findings with evidence, priorities, and acceptance criteria your developers can use.
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 · retestedObserved → changed
Before: language selected by a query parameter
/services/seo-services?lang=zhAfter: a dedicated Chinese URL
/zh/services/seo-servicesLegacy request → 308 redirect → Chinese page with matching canonical and language alternates.
- 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.
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.
Illustrative triage · not client findings
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.
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.
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.
03Schedule with related work
A secondary page has a long title but remains accessible and relevant.
Improve the title in its content review. A length warning alone does not establish a critical technical failure.
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.
01Agree on the baseline
You provide the site, symptoms, recent changes, and available access. We define page groups and evidence gaps.
02Investigate and document
We inspect representative URLs and shared rules, then record findings and the confidence behind each recommendation.
03Hand off the work
You receive an issue register, a priority queue, developer-ready records, and scope limitations. Together we confirm owners.
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 scopeCan 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. A detailed audit is part of the agreed project, not an automatic result of booking.
Keep Exploring SEO Services
Explore adjacent capabilities in the same service family, or return to the parent page for the complete program.
