Execution Prompt — Some pages are missing a canonical tag
Context
Use this document to implement the issue below in a coding agent (Cursor, Claude Code, Codex, or similar).
Treat it as an operational handoff: apply the fix, respect constraints, and validate against the grouped evidence.
Project
·Name: RoadRunner Inc·Domain: roadrunnerinc.com·Site URL: https://roadrunnerinc.comDecision
·Title: Some pages are missing a canonical tag·Decision key: dec_canonical_misconfigurationWhat this means
RankQuest found indexable pages that do not have a canonical tag in the HTML head (or the href is empty). Canonical issues are grouped by type so you can fix patterns, not chase individual URLs in isolation.
Why this matters
Without a canonical tag, search engines must guess which URL is the main version of each page. That can dilute ranking signals or index the wrong URL when multiple versions exist.
Expected Outcome
Every affected page serves a correct, absolute canonical tag pointing to its own final URL on the production host (or the intended canonical target for that page type). Homepage canonical behavior stays correct. No cross-domain or malformed canonicals remain on the listed URLs.
Affected Evidence
Implement the fix for every affected URL group below. Use the grouped evidence as the authoritative URL list.
Pages with missing canonical tags
6 affected URLs
These pages render without a self-referencing canonical tag in the HTML head, so search systems must infer the preferred URL.
·/blog·/map·/control·/orphaned/1·/orphaned/2·/pricingExisting Implementation Context
Canonical rules summary (Entire decision)
·Self-canonical on all indexable HTML templates under roadrunnerinc.com·Emit exactly one link rel="canonical" per page from the layout or CMS head partial·Use absolute URLs on the production host after redirects resolveImplementation Requirements
·Open Evidence to review affected pages grouped by canonical issue type·Add exactly one canonical tag in the head of each listed page·Set each href to that page's own final URL (absolute, on your site's domain)·Re-crawl or wait for the next observation after you publish the change·One canonical per page — avoid duplicate or conflicting canonical tags·Use absolute production URLs on roadrunnerinc.com, not relative paths alone·Do not: Point inner pages to the homepage as their canonical unless that is deliberateDecision-Specific Instructions
·Use production origin https://roadrunnerinc.com for absolute canonical URLs unless evidence shows a different live host.·Inspect where canonical tags are generated (templates, layout, CMS, or static site generator).·Ensure non-homepage pages self-canonicalize to their final absolute URL on the production host.·Preserve correct homepage canonical behavior.·Avoid cross-domain canonicals unless intentionally configured.·Validate each affected evidence group after implementation.Output Required From Agent
Return a concise implementation plan with:
1.**Template / CMS changes** — where canonical output is generated for each affected page type2.**Per-URL canonical href** — absolute production URL for each path in the evidence groups3.**Verification checklist** — how to confirm canonicals after deploy (view-source or crawl)4.**Rollback notes** — what to revert if a template change affects unrelated pagesDo not invent URLs beyond the evidence lists. Do not expand scope to hreflang, redirects, or sitemap work unless required to fix the listed canonical issues.