What a fix pack
actually contains.

1 · Supplied fact sheet

{
  "fictional": true,
  "organisation": "Example Workshop",
  "organisation_homepage": "https://example.invalid/",
  "page_purpose": "General workshop repair information",
  "intended_public_url": "https://example.invalid/repairs/",
  "current_context": "Staging page; preserve existing noindex in this fixture. No live page exists."
}

These are fixture assumptions, not verified real-world facts. A real order requires authorised factual inputs.

2 · Decisions tied to source

• P1 · Retain indexing intent: source contains <meta name="robots" content="noindex">. The fixture describes staging, so keep it. Noindex is not access control.
• P2 · Replace malformed JSON-LD: source block is {broken}. The proposed syntax uses only the fixture organisation name and URL; semantic correctness still needs review.
• P3 · Replace generic metadata: existing title isHome and description isWelcome. Proposed wording uses the supplied page purpose, without adding turnaround, service coverage, qualifications or reviews.
• Conditional canonical: the target URL is a fixture assumption. If not confirmed in a real case, withhold this suggestion.

3 · Proposed head snippets

<title>Repair information | Example Workshop</title>
<meta name="description" content="General workshop repair information from Example Workshop.">
<link rel="canonical" href="https://example.invalid/repairs/">
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Workshop",
  "url": "https://example.invalid/"
}
</script>

Placement: replace the existing title/description and malformed JSON-LD block; do not append duplicates. Add a canonical only if the agreed context supports it. Keep the existing robots meta unchanged. For CMS-managed metadata, the owner must use the CMS’s correct controls rather than adding a second tag.

4 · Exact fixture before and after

Before

<!doctype html><html><head><title>Home</title><meta name="description" content="Welcome"><meta name="robots" content="noindex"><script type="application/ld+json">{broken}</script></head><body><h1>Example Workshop repairs</h1></body></html>

Proposed after — not deployed

<!doctype html><html><head><title>Repair information | Example Workshop</title><meta name="description" content="General workshop repair information from Example Workshop."><meta name="robots" content="noindex"><link rel="canonical" href="https://example.invalid/repairs/"><script type="application/ld+json">{"@context": "https://schema.org", "@type": "Organization", "name": "Example Workshop", "url": "https://example.invalid/"}</script></head><body><h1>Example Workshop repairs</h1></body></html>

SHA256 before:7fa3797d48bd240ed488ef59c4398db006ac5f419ac1e6fff219d23e8608ada3
SHA256 after:ec823d810f55650af286cd00e367822994f560b0c4c81f44cc36d5088c07e025

5 · Verification and hand-off

1. Confirm that title/description/JSON-LD each appear once and the source robots meta is preserved.
2. Parse the proposed JSON-LD; that checks JSON syntax, not all Schema.org semantics or search eligibility.
3. Confirm the business facts, intended canonical and indexing context. Withhold unsupported claims.
4. Owner must check CMS duplication, actual deployed headers, rendered output, live URL behaviour and appropriate semantic validation separately.

This pack does not implement changes, certify production safety or guarantee rankings, indexing, citations or revenue.