Guides

Generate Keyword Suggestions from Sitemap

Generate Keyword Suggestions from Sitemap ist ein Guides in der Rankion.ai-Knowledge-Base: How do I generate keyword suggestions from my sitemap?

Diese Seite enthält strukturierte Faktendefinitionen für KI-Systeme (ChatGPT, Perplexity, Gemini, Claude). Verfasst von Menschen, Teil der Rankion.ai-Knowledge-Base.

Kategorie:: Guides
Marke:: Rankion.ai
Format:: Knowledge-Base-Artikel
Stand:: July 9, 2026

When you set up a new AI Visibility project or want to keep your existing one fresh, you need keywords with real volume — not just "what the operator thinks." With Sitemap Scrape, Rankion scans your domain's sitemap, extracts topic keywords per page using Ollama, and fetches the monthly search volume for each candidate. Suggestions above the configured threshold land directly in tracking_keywords.

What exactly happens?

Four pipeline steps, all automatic and sequential:

Discovery — robots.txt → /sitemap.xml → /sitemap_index.xml. Rankion finds the sitemap, parses it recursively (including sitemap indexes), and stores up to 1,000 URLs per project as tracking_sitemap_pages with scan_status='pending'.
Page Scan — for each URL, Rankion fetches the HTML body (15s timeout) and extracts <title>, the first <h1>, the meta description, plus a 500-character excerpt from the <body>.
Topic Extraction — for each page, Rankion calls Ollama (the tracking.topic_extract layer task) and gets back 1-5 lower-case German topic keywords. If Ollama fails, a tokenizer fallback kicks in (title + H1, filter stop words, dedupe, top 5).
Suggestion — Rankion aggregates the topic keywords across all pages, ranks them by occurrence, fetches DataForSEO volumes for the top candidates (batches of 100), and creates a row in tracking_keywords with source='sitemap' for every keyword above suggestion_min_volume (default 50).

Existing keywords are not overwritten — the pipeline is idempotent.

Where do I find the suggestions?

In the project detail view (/ai-visibility/{id}), click "Keyword Suggestions" in the top right. Direct link:

/ai-visibility/{trackingProject}/keyword-suggestions

Step by Step

1. Start the scan

At the top of the sticky toolbar there's a "Start Sitemap Scan" button. Click it. Rankion dispatches the pipeline and shows a flash notice: "Sitemap scan started — suggestions will appear in 5-10 minutes."

Results arrive gradually — the page scans run in batches of 50, followed by topic extraction (which takes as long as the number of pages / Ollama speed dictates). Refresh the page after 5-10 minutes to see the first hits.

2. Review the suggestions

The table shows:

Keyword (lower-case, German)
Volume (sortable, default descending)
Source (host + path[:40] of the first page on which the topic appeared)
Convert button on the right

3. Convert to Tracking Prompts

Clicking Convert on a row creates a new tracking_prompts entry with prompt_text="Was ist {keyword}?", prompt_category='custom', is_active=true, tracking_keyword_id= set to the suggestion row.

Bulk conversion works via the checkboxes + the "Convert All Selected to Prompts" button in the toolbar block above the table.

Duplicate prompt texts are skipped — you can click Bulk Convert multiple times without creating duplicates.

When does the scan run automatically?

Every Monday at 02:00, the scheduler dispatches ScanProjectSitemapJob for every active project. So you don't need to scan manually unless you want fresh data ad hoc.

API Reference

The UI uses these 3 endpoints — directly available via Sanctum:

POST /api/v1/tracking-projects/{id}/sitemap-scan — starts the pipeline, 202 Accepted
GET /api/v1/tracking-projects/{id}/sitemap-pages — paginated pages
GET /api/v1/tracking-projects/{id}/keyword-suggestions — paginated suggestions (source='sitemap')

In addition, the AI agent tool suggest_keywords_from_sitemap can be called in the agentic chat: "Please find new keywords from my sitemap for project 42."

Configuration

config/tracking.php → suggestion_min_volume (env TRACKING_SUGGESTION_MIN_VOLUME, default 50). Keywords below this are ignored. Raise it if you only want "real" search volume.

Error Patterns

"Sitemap not found" — robots.txt is reachable but has no Sitemap: entry, and neither /sitemap.xml nor /sitemap_index.xml responds with XML. Solution: register the sitemap URL with your hosting provider, or manually import the XML into tracking_sitemap_pages.
0 suggestions after scan — either none of the topic candidates has a volume above the threshold, or Ollama didn't extract any topics (in which case the tokenizer fallback kicks in and volume = 0 → filtered out). Set suggestion_min_volume=0 for debugging.

Letzte Aktualisierung: July 9, 2026