# SearchSignal SEO Strategy

## Strategic objective

Own the emerging category around **SEO MCP servers, SEO APIs for AI agents, and agent-native SEO workflows**, while also competing on durable commercial intents such as AI keyword research, technical SEO audits, competitor analysis, rank tracking, backlink intelligence, and SEO tools for major AI clients.

## Architecture

### Commercial hubs

- `/` — category and brand demand
- `/platform/` — broad AI SEO platform intent
- `/features/` — capability hub
- `/integrations/` — client connection hub
- `/solutions/` — audience hub
- `/pricing/` — plan and value intent
- `/connect/` — setup and activation intent
- `/docs/` — developer implementation intent

### Category pages

- `/seo-mcp-server/` — commercial SEO MCP category page
- `/seo-api/` — commercial SEO API page
- `/free-keyword-research-tool/` — free acquisition page

### Educational authority

- `/resources/seo-mcp-server-guide/`
- `/resources/seo-api-for-ai-agents/`
- `/resources/agentic-seo-workflow/`

### Integration pages

- Cursor
- Claude Desktop and Claude Code
- ChatGPT and custom HTTP-agent workflows
- Windsurf
- VS Code and Copilot-compatible workflows

### Feature clusters

- site audit
- opportunities
- keyword research
- competitor analysis
- rank tracking
- backlinks
- content workflows

## Search-intent separation

Avoid creating multiple pages that answer the same query in the same way.

- The commercial SEO MCP page answers **why buy and connect**.
- The SEO MCP guide answers **what it is, how it works, and how to evaluate it**.
- Integration pages answer **how to use it in a named client**.
- Docs answer **how to configure and call the product**.
- Feature pages answer **what each capability does**.

Before adding a URL, define:

1. primary query;
2. searcher stage;
3. page type;
4. unique promise;
5. internal-link parents and children;
6. conversion event;
7. existing page that could overlap.

## On-page standards

Every indexable page must include:

- one unique title and H1;
- a distinct, useful meta description;
- a self-referencing canonical;
- descriptive internal links from at least one hub and two contextually related pages;
- a visible conversion path appropriate to intent;
- real product detail, setup steps, or decision support—not filler;
- valid structured data only when the visible page supports it;
- original visuals or representative product illustrations;
- an update owner and review date.

## Structured data

Use:

- Organization and WebSite sitewide;
- SoftwareApplication on commercial product pages;
- FAQPage only when the questions and answers are visible;
- BreadcrumbList on hierarchical pages;
- TechArticle on long-form technical resources.

Do not add review, rating, customer, security, price-validity, or performance schema without real supported data.

## Internal-link rules

- Every feature links to the platform, relevant integrations, one solution, and one resource.
- Every integration links to connect, docs, platform, and the strongest relevant feature.
- Every resource links to one commercial page, one setup page, and at least one related guide.
- Hub pages use descriptive anchors, not repeated “learn more.”
- Do not force exact-match anchors into every paragraph.

## Content quality bar

SearchSignal should publish fewer, better pages. Each resource must contain a practical model, framework, configuration, evaluation method, template, or workflow that is useful even before the reader signs up.

Reject content that:

- paraphrases a generic definition without adding an operating model;
- creates a page for every trivial keyword variant;
- claims tools or clients are supported without testing current configuration;
- uses fabricated case studies;
- hides uncertainty in AI-generated recommendations;
- publishes many near-duplicate pages to manufacture topical authority.

## Technical SEO

- Static marketing pages remain indexable and fast.
- `/app`, authentication, account, token, billing, API, and private project routes remain noindex and no-store.
- One preferred HTTPS host and one trailing-slash policy.
- Correct status codes; no soft 404s.
- XML sitemap contains only canonical indexable URLs.
- Robots exclusions supplement but never replace authentication.
- Open Graph images stay public.
- `llms.txt` explains the product accurately but is not treated as a ranking shortcut.
- Add content hashes to CSS/JS when the frontend moves into the production build system.

## Measurement

Primary funnel:

1. landing-page view;
2. high-intent CTA click;
3. signup start;
4. account created;
5. project added;
6. token created;
7. config copied;
8. first successful MCP/API call;
9. first audit or workspace pack retrieved;
10. returning active workspace;
11. Pro upgrade when data depth is needed.

SEO reporting must distinguish brand, category, integration, feature, resource, and solution clusters. Measure activated users—not just visits or signups.