Docs

How to rank higher with HeyRank

A practical guide to every part of HeyRank — with example prompts and a weekly workflow. Read top to bottom, or jump via the contents.

01

Getting started

Sign in with Google, add a site, and connect Search Console so HeyRank can work from your real queries and pages.

HeyRank helps you rank higher on Google. It connects to Search Console to explain your rankings, finds the pages closest to moving up, recommends specific changes, and tracks positions after you ship them.

After you sign in, onboarding walks you through five steps: add your domain, fill About (category + description), list competitors, optionally add connectors, then connect Search Console for that property.

You can skip GSC, but recommendations stay generic until it is connected. First GSC connect adds a message bonus on Free.

  • Free includes 5 messages per month (+2 when Search Console connects).
  • Site limits: Free 1 site · Pro 3 · Ranker 10.
  • Search Console OAuth is read-only and scoped per site.

Examples

First-week setup

  1. Sign in with Google → complete onboarding for your primary domain.
  2. Confirm the matching Search Console property (domain or URL-prefix).
  3. Open Home and skim Today — or start a chat with “What should I fix first?”

02

Sites & workspace

Every chat, Action, and report is scoped to the active site. Switch sites from the sidebar.

Use the site switcher at the top of the sidebar to change the active site, or press ⌘K to jump anywhere.

The sidebar groups every tool: Home, Ask HeyRank and Actions; Opportunities, Content, Indexing and Backlinks under Grow; Site settings and Account & billing under Configure.

Site settings holds the active site’s Search Console, profile, competitors and publishing connectors. Account & billing covers your profile, plan, credits and API keys.

  • Keep About + competitors accurate — drafts and gap analysis use them.
  • Competitors are domains (e.g. rival.com), not full article URLs.

Examples

Add a second site (Pro / Ranker)

  1. Sidebar → site switcher → Add site.
  2. Enter the domain, review AI-suggested About + competitors, save.
  3. Connect Search Console for that site before trusting Today or recipes.

03

Home & Today

Home is your base: search performance, a GSC-backed Today queue, open Actions, setup steps and usage.

Today ranks this week’s focus: CTR gaps, striking distance, open Actions, and Watchlist alerts when Search Console is connected.

Queue items into Actions from Today, or export a CSV when stakeholders want a static list.

Without GSC, Home still shows setup steps and chat entry points — Today stays empty until data is available.

Examples

Monday triage

  1. Open Home → review Today.
  2. Queue the top 3–5 items into Actions.
  3. Open New chat only for items that need a rewrite brief or deeper dig.

04

Chat

Ask SEO questions grounded in your Search Console window. One message uses one credit.

New chat starts an empty thread. Pick a specialist agent — Strategy, Keywords, Technical, Content, Competitors, AI visibility or Backlinks — or leave it on Auto. Each specialist focuses on its job with its own tools and starter questions; the choice is saved per conversation.

Each reply can surface follow-ups you can click to continue. Use Share in the chat header to create a read-only public link (and disable it any time).

With GSC connected, HeyRank can pull performance, top pages/queries, CTR gaps, striking distance, cannibalization, and related recipes — then propose Actions.

Chat is for decisions and drafts. Durable work belongs in the Actions queue so it survives when you leave the thread.

  • Be specific: name the URL or query when you can.
  • Prefer “what to fix this week” over open-ended “audit my whole site.”

Examples

Weekly priority

What should I fix first on this site this week?

CTR gaps

Which queries have strong impressions but weak CTR?

Striking distance

Show pages ranking positions 8–20 that could move with a focused rewrite.

GEO / citability

Audit /blog/pricing-guide for answer clarity, FAQ, and schema gaps for AI search.

Cannibalization

Are any of my pages competing for the same primary queries?

05

Actions board

Every recommendation becomes a card on a board — To do, In progress, Done — scored by impact and effort.

Actions hold ranked SEO work: title/CTR rewrites, content gaps, GEO fixes, index follow-ups, and optional CMS updates. Each card carries its impact, effort, the evidence behind it, and acceptance criteria that define done.

Quick wins (high impact, low effort) sort to the top. Drag cards between columns or use Start / Done. CMS updates show a before/after preview and wait for your approval.

When you mark an Action done, HeyRank records a Search Console baseline and later shows what moved. Export CSV when you need the backlog elsewhere.

Every open Action includes a ready-to-paste fix prompt: copy it, or open it straight in Claude or ChatGPT, and let your AI assistant (Claude Code, Codex, Cursor…) implement the change in your codebase or CMS.

  • Treat Actions as the source of truth — chat is the workshop.
  • On smaller screens, open Actions from the chat header sheet.

Examples

From chat to done

  1. Ask for CTR gaps → accept queued Actions in the rail.
  2. Open an Action → review the brief → rewrite title/meta offline or via connector preview.
  3. Mark Done when live; check Impact later against GSC.

06

Google Search Console

Per-site read-only OAuth. Grounds Today, chat recipes, Index, Watchlist, and Backlinks.

Connect under Site settings → Search Console (or during onboarding). Pick the property that matches the site hostname.

Tokens are stored encrypted. HeyRank does not keep a permanent warehouse of your full click history.

Disconnect anytime from the same tab; recipes fall back to general guidance until you reconnect.

Examples

Property mismatch

  1. If data looks empty, confirm you connected sc-domain:example.com vs https://www.example.com/ as appropriate.
  2. Wait for GSC’s usual reporting lag (often 2–3 days) before judging freshness.

07

Index coverage

Compare sitemap URLs with URL Inspection to find pages that should be indexed but are not.

Open Indexing from the sidebar. Run a scan against your sitemap, then inspect sample URLs.

Quotas: Free 1 scan/month (10 URLs) · Pro 20 scans (40 URLs) · Ranker 100 scans (100 URLs).

Queue follow-up Actions when inspection shows blocked, not found, or discovered-not-indexed issues you can fix.

Examples

New section went live

We shipped /guides last week — which of those URLs are still not indexed?

09

Content gap

Compare your page to a competitor for topic and citability gaps, then queue Actions.

Open Content → Competitor gap. Paste your URL and a competitor URL, or batch from your competitor list.

Results highlight missing angles, thin answers, and GEO/citability issues you can turn into Actions or chat drafts.

Export CSV when you want a research trail outside the app.

Examples

Head-to-head

  1. Content gap → your /pricing vs competitor /pricing.
  2. Queue the highest-impact gaps as Actions.
  3. In chat: “Draft an FAQ section that closes the top two gaps.”

10

Watchlist

Pin queries or pages and surface 7-day GSC deltas as Today alerts.

Open Opportunities → Watchlist. Add QUERY or PAGE items you care about week over week.

When deltas matter, they appear in Today so you do not have to re-run the same chat every Monday.

Keep the list tight — a few strategic pins beat dozens of noisy ones.

Examples

Launch watch

  1. Add the primary query and the new landing page URL.
  2. Check Home → Today mid-week for movement.
  3. If CTR drops after a title change, open chat with the URL for a revision brief.

11

Writing style

Set tone, point of view, vocabulary, and a sample paragraph so chat and drafts match your brand voice.

Open Content → Writing style. Choose tone and POV presets, add preferred vocabulary, words to avoid, and an optional sample paragraph.

Use Generate with AI to draft a style guide from your About page and category.

When set, HeyRank injects the guide into chat and article generation for that site.

  • Paste a real paragraph from your site — it beats abstract adjectives.
  • Pair Writing style with accurate About + competitors for the best drafts.

Examples

Launch a new site voice

  1. Fill About in onboarding or Site settings.
  2. Writing → Generate with AI → edit tone and sample paragraph → Save.
  3. In chat: “Draft a blog post about [topic] in our voice.”

12

Connectors (CMS & MCP)

WordPress, Shopify, and custom MCP let HeyRank create drafts — apply stays human-gated.

Connect under Site settings → Publishing (or late in onboarding).

WordPress: draft posts and propose title / excerpt / body updates with a preview before anything goes live.

Shopify: article drafts. Custom MCP: expose create_draft (and related tools) for your stack.

Nothing publishes without your approval in the preview flow.

  • Connectors are available on every plan — connect during onboarding or anytime in Site settings.
  • Prefer preview diffs over pasting blind HTML from chat.

Examples

Title rewrite → WordPress

  1. Chat queues a CTR rewrite Action for a post.
  2. Open the Action → Apply → review title/excerpt/body preview.
  3. Approve the draft or update — then mark the Action Done.

13

Credits & plans

One chat message = one credit. Every feature is on every plan — upgrade for more messages, sites and scans.

Free: 5 messages/month (+2 on first GSC connect), 1 site, light Index/Backlinks quotas.

Pro ($29/mo): 100 messages, 3 sites, higher scan and brief quotas, API & MCP keys.

Ranker ($99/mo): 500 messages, 10 sites, the highest Index/Backlinks quotas.

Yearly billing costs 10 months instead of 12; credits still refill every month.

Credit packs are one-time top-ups on any plan. Purchased credits never expire and carry over every month, even if you cancel.

Manage billing in Account & billing (Stripe customer portal). Cancel anytime; access continues through the paid period.

Examples

When to upgrade

  1. Hitting the Free message cap mid-month → Pro.
  2. A busy month on any plan → buy a credit pack instead of upgrading.
  3. Need more than 3 client sites → Ranker.
  4. Only need API/MCP for automation → Pro is enough to create keys.

14

API & MCP (optional)

Pro and Ranker can drive HeyRank from Cursor, Claude, or your own tools.

Create API keys under Account & billing → API & MCP.

MCP endpoint and Cursor config live on the MCP + SDK page. REST lives under /api/v1.

Same product rules apply: site scope, credits, and human-gated CMS apply.

  • Start in the web app until the workflow is clear, then automate repeatable asks via MCP.
  • See /mcp for endpoint URLs and SDK examples.

15

Recommended weekly workflow

Add site → Ask in chat → Queue in Actions → Apply when ready.

Monday: Home → Today → queue 3–5 Actions. Skim Watchlist alerts.

Mid-week: clear Actions (rewrites, drafts, index fixes). Use chat only when you need a fresh brief.

Before publish: connector preview or paste carefully. Mark Done.

Friday: optional Backlinks refresh or Content gap on one priority URL. Export CSV if you report out.

Examples

Agency cadence

  1. Per client site: Today → Actions → share Backlink Brief if outreach is outsourced.
  2. Keep one chat thread per initiative; do not treat chat history as the backlog.

Start ranking higher this week.

Connect Search Console in under two minutes and see exactly what will move your pages up. Free to start.

Free to start · no credit card · read-only Google access