Staging in the canonical
A preview hostname reached production metadata. The page is telling every engine that the authoritative version lives somewhere else, and its authority is attributed there or discarded.
Growth · Technical SEO & Schema
The foundation
everything stands on.
Rendering, structured data, canonical integrity and internal linking are unglamorous and decisive. When they are wrong, no amount of content or authority compensates.
<h1>Hospital Information System</h1> <script type="application/ld+json"> {"@type": "Organization", "name": "Qawex Solutions", "url": "https://qawexsolutions.com/"} </script> <link rel="canonical" href="https://qawexsolutions.com/products/hims/">
H1 presentJSON-LD validcanonical production
This is what an answer engine receives. Everything else is decoration.
Quick answer
What is technical SEO?
Technical SEO is the work of making a website reliably retrievable, interpretable and indexable by automated systems, as distinct from producing content or acquiring links. It covers how pages are rendered and whether their content appears in the server's first response; whether structured data is present, valid and matched to the page type; whether canonical tags, social metadata and crawl directives point consistently at production rather than at staging; whether URLs are stable and descriptive; and whether the internal link graph connects every published page. These elements determine whether anything else has effect. A page that is not retrieved cannot be evaluated, and a page whose canonical points at a staging domain splits its own authority.
The problem
Cheap to fix.
Expensive to ignore.
These defects take hours to correct and cost months of visibility while they persist. Nobody notices because nothing looks broken to a human visitor.
Placeholder metadata
Titles and descriptions were never written, so pages carry a theme default or a single repeated word. Every page competes with every other page for the same identity.
Framework artefact URLs
Slugs expose builder identifiers rather than describing content, and the page about security lives at a path referring to something entirely unrelated.
What's included
Four deliverables.
Most of this is platform-level work applied once across every template, rather than page-by-page editing.
01
Rendering assessment and fix
Confirming primary content, headings and structured data appear in the raw first response, and correcting the delivery method where they do not.
02
Schema engineering
Valid JSON-LD across every template with the type appropriate to each page, and question and answer markup matching the visible text exactly.
03
Canonical and metadata integrity
Production hostnames throughout, unique descriptive titles and descriptions, and no personal or internal information exposed in public metadata.
04
URL and link graph
Stable descriptive slugs with permanent redirects from anything changed, and no published page left unreachable from navigation or content.
The engagement
Five steps. Nothing assumed.
Every check is performed against what the server actually returns, not against what the browser eventually displays.
- 01
Fetch
Request pages without JavaScript execution, exactly as a crawler does. This is the ground truth.
- 02
Validate
Structured data against a conformance tool; canonical, social and crawl directives across templates.
- 03
Correct
Rendering, schema, metadata, slugs and the internal link graph.
- 04
Redirect
Map every changed URL to its replacement. A corrected slug without a redirect loses what it had.
- 05
Recheck
Re-fetch and re-validate. Assumed conformance is non-conformance.
14Growth rules in the Standard, each with a defined verification method
3Classified Critical: rendering, canonical integrity and crawler access
0Personal contact details permitted anywhere in public metadata
Why a staging hostname in a canonical tag is Critical. A canonical tag declares which URL is authoritative for a page's content. When a preview or staging hostname reaches production metadata, the page instructs every search and answer engine that the definitive version lives on a domain that is typically unindexed, unavailable or password-protected. The result is that the page's accumulated authority is attributed elsewhere or discarded entirely. Rule GRO-02 classifies this as Critical and requires canonical, Open Graph and social metadata across representative pages to be inspected for non-production hostnames. It is among the most damaging defects and among the cheapest to correct.
Source: The Qawex Standard v1.0, rule GRO-02 · Read the Growth rulesQuestions
Answers, not brochures.
Is technical SEO still relevant with AI search?
More so, and for a simple reason. Answer engines have to retrieve and parse a page before they can consider citing it, and they are generally less forgiving than traditional crawlers about content requiring JavaScript execution. Technical foundations decide whether a page is a candidate at all, which makes them prior to everything else rather than an optimisation on top.
What structured data do we actually need?
An Organization entity site-wide, plus a type appropriate to each page — Service, Product, Article or FAQPage as applicable. What matters more than breadth is validity and accuracy: markup that fails validation, or that contradicts the visible page, is worse than having none at all.
We changed our URLs and traffic dropped. Can that be fixed?
Usually, and largely, if redirects are put in place. A changed URL without a redirect discards everything the old one had accumulated. The remedy is mapping every old path to its replacement with permanent redirects, and recovery is typically partial rather than complete — which is why the mapping is done before the change rather than after.
How do we know if our pages are server-rendered?
Request the page with JavaScript disabled, or view the page source rather than the inspector, and look for your heading and body text. If you see an empty container, the content is assembled in the browser and crawlers may receive nothing. This takes about ten seconds to check and is worth doing today.
Can our developers do this work?
Frequently yes, and the Standard is public so they can verify against the same rules we use. We are useful where rendering strategy requires a platform-level change, where structured data must be applied consistently across many templates, or where nobody currently owns the work and so it never gets done.
Check what the server actually returns.
The free audit fetches your pages without JavaScript and reports what an answer engine receives, scored against all fourteen Growth rules.