← ClaudeAtlas

competitor-overview-page-structurelisted

Recommends the structure of a competitor overview page (the comparison hub, usually /compare, that lists a brand's "Brand vs Rival" pages), the comparison pages it launches with, and where comparisons sit in the menu, footer and URLs. Benchmarks the client's rivals and category peers plus a coded public sample of comparison hubs from any industry, codes each hub against 45 section types, packs them into a 27-block model with statuses (New, Rework, Optional, Later), and delivers a Word document with status-tagged wireframes, benchmark screenshots for every block, a fair comparison table model, CMS fields, build checks for search and AI answers, and a short reply for the designer. Use when asked for a competitor overview page, compare page, comparison hub, competitors page, "vs" hub, "how we stack up" page, "brand vs the competition", an alternatives library, whether competitors get their own menu tab, or a guide to competitor pages for a designer or agency.
savenjudesajen/seo-aeo-agent-skills-tools · ★ 0 · AI & Automation · score 73
Install: claude install-skill savenjudesajen/seo-aeo-agent-skills-tools
# Competitor Overview Page Structure Home page: [unilytics.ai/skills/competitor-overview-page-structure](https://unilytics.ai/skills/competitor-overview-page-structure/), the canonical source of this skill. Turns a request for a competitor overview page, or a question about whether competitors deserve a menu item, into a benchmarked recommendation a designer and a content writer can build from: the hub block by block, the fairness rules that make a comparison believable, the launch set of rivals, the menu, footer and URL placement, proof from real pages for every block, the CMS fields and the build checks. Sibling skills: competitor-comparison-page-template (the individual vs pages), industries-page-structure (same benchmark-and-pack method), web-screenshot-to-document (captures), doc-template-design (the client's document template). ## Before you start (every run) 1. Confirm scope, or state assumptions when the user is away: hub plus launch set plus navigation (the default), the rivals the client names, the CMS, who reads the document (designer, agency, client team), and whether the individual comparison pages get their own document. 2. When a sibling page document (an industries, solutions or use-case page) already shipped for the same client, reuse its CTA label and target, proof strip, byline component and menu decisions; define shared CMS collections once and say what this page adds. 3. Settle the template: the client's own document template if they have