Interactive toolFreeNo sign-up16 SEO jobs
The SEO Prompt Builder
Type in your site once and all 16 prompts rewrite themselves for you. Pick a job, copy the prompt, paste it into Claude. That’s it.
- 1
Enter your detailsWebsite, market, topic and two competitors.
- 2
Pick a jobFilter by category below.
- 3
Copy and paste into ClaudeClaude pulls the DataForSEO data and does the work.
2Pick a job
Keyword research
Keyword research and clustering
Turn a seed topic into a short list of pages worth building.
BringA topic, your website and a description of what the business sells.
Ask Claude
Research [TOPIC] for [DOMAIN], targeting [MARKET]. Start with a small relevant sample, then pull up to 200 keyword suggestions and available volumes. Group by intent, check representative live SERPs, and map each group to an existing or proposed page. Explain what to build first and which terms to exclude. Export a keyword CSV and a prioritized page map. Report sources, limits and API cost; do not sum close-variant volumes.
You getA keyword CSV and a prioritized page map.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Striking-distance opportunities
Find existing pages where a focused edit is worth testing.
BringA Search Console export with page, query, country, device and dates.
Ask Claude
Use my Search Console export for [DOMAIN] in [MARKET]. Find page-query pairs with average position 8 to 20 and meaningful impressions during the last complete 28 days. Compare with the preceding 28 days, group by page, and check a representative live SERP for the strongest candidates. Recommend five pages to investigate. Draft specific title or content edits and explain the evidence. Keep observed changes separate from hypotheses. Save a CSV and report API cost.
You getFive page recommendations with draft edits and evidence.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Data: ~$0.02 data (Run 1)Walkthrough
Competitor keyword gap
Find relevant gaps without copying a competitor's whole strategy.
BringYour domain and two genuine search competitors.
Ask Claude
Compare [DOMAIN] with [COMPETITOR 1] and [COMPETITOR 2] in [MARKET], focusing on [TOPIC]. Find relevant queries the competitors rank for that our returned ranking data does not show. Filter out unrelated services, locations and branded navigation. Inspect the live results for the best candidates. Give me the top 20 opportunities, the page to update or create, and the reason each belongs in our plan. State coverage, filters, sources and API cost.
You getA ranked opportunity list mapped to pages.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Data: ~$0.27 dataWalkthrough
Technical SEO
Crawl audit to fix list
Turn hundreds of crawler warnings into work someone can implement.
BringA crawl export, important templates and available performance data.
Ask Claude
Analyze this crawl of [DOMAIN] alongside the supplied Search Console or analytics data for [MARKET]. Group issues by template and likely cause. Create the ten most useful implementation tickets, each with affected URLs, evidence, a proposed fix, priority, confidence and a verification step. Distinguish observed problems from hypotheses. Where performance data is unavailable, prioritize by technical impact and business importance rather than invented traffic estimates. Export the tickets and supporting URL list.
You getTen implementation tickets with checks for completion.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Migration redirect map
Match old URLs to useful destinations and isolate the uncertain cases.
BringOld and new crawls with titles and main content.
Ask Claude
Build a redirect proposal for [DOMAIN] using these old and new crawl exports. Match URLs using paths, titles, main content and visitor intent. Include a reason and confidence for every match. Leave genuinely unmatched or uncertain URLs for review. Check destinations for status, indexability, redirect chains and loops. Export a redirect CSV and an exceptions file. Prepare the proposal for review without applying changes.
You getA redirect CSV and a separate exceptions file.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Structured-data review
Generate markup that fits the actual page and current requirements.
BringRepresentative page content and existing structured data.
Ask Claude
Review the visible content and existing structured data on these [DOMAIN] templates. Check current official requirements before recommending types. Identify missing, conflicting or unsupported markup, then propose only the JSON-LD supported by the actual page content. Validate syntax and distinguish valid markup from rich-result eligibility. Do not invent product, review, organization or author facts. Deliver a report and proposed changes for review, without publishing them.
You getA validation report and proposed JSON-LD changes.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
AI crawler log check
See which sections bots requested and what responses they got.
BringA server-log sample and your robots.txt or crawler policies.
Ask Claude
Write and run a parser for these [DOMAIN] server logs. Separate training crawlers, search crawlers and user-directed fetch agents using current official documentation. Summarize requests by agent, site section, date and status code. Flag blocked requests and unverified user-agent-only identifications. Compare with the supplied crawler policies. Do not infer citations, referrals or revenue from crawl hits. Save the parser, summary tables and a short investigation list.
You getA reusable parser and a report by bot, section and status.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Content + AI visibility
Brief from the live SERP
Give a writer a clear angle and the evidence to back it.
BringA topic, target audience, source material and URL inventory.
Ask Claude
Build a content brief for [TOPIC] for [DOMAIN], targeting [MARKET]. Use current live results and available keyword data to determine intent and page format. Combine that research with the supplied expertise, interviews or original examples. Recommend an original angle, section outline, required evidence and internal links from our URL inventory. Flag claims needing an expert or more research. Save a writer-ready brief with source links and API cost.
You getA writer-ready brief with sources and internal links.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Bulk titles and descriptions
Prepare metadata edits that keep each page's purpose intact.
BringA crawl export and the top queries for each page.
Ask Claude
Join this [DOMAIN] crawl export to the supplied Search Console page-query data for [MARKET]. Propose titles and meta descriptions for the 20 pages with the clearest need. Keep wording accurate, distinct and matched to page intent. Aim for concise display lengths without treating character counts as guaranteed Google limits. Preserve brand and product facts. Export current text, proposed text, target query and reason in a CSV. Leave uncertain pages for review.
You getA before-and-after CSV with a reason for each change.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
AI citation tracking
Track a defined sample without confusing mentions with citations.
BringTen customer questions, a platform and a fixed measurement method.
Ask Claude
For [DOMAIN] and [TOPIC] in [MARKET], propose ten useful customer questions for AI visibility checks. Specify a supported DataForSEO measurement method before collecting data, then keep that method consistent. Record platform, model or interface, location, date, answer and cited URLs. Distinguish brand mentions, retrieved search results and actual citations. Save the results and a repeatable tracking plan. State sample limits and API cost; do not present one run as total market visibility.
You getAn answer-and-citation log ready for repeat checks.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Original research study
Investigate a useful question with reproducible evidence.
BringA hypothesis and a defined list or sample of public sites.
Ask Claude
Help design a small original study about [TOPIC] for [DOMAIN]. Define the hypothesis, sample, measurements and limits before collecting data. Use supplied sites or a documented selection process, with DataForSEO and direct public-page checks where appropriate. Save raw observations, sources and retrieval dates, then produce tables and a draft methods-and-findings summary. Separate observation from causation. Treat missing search results as inconclusive evidence of indexing, and report API cost.
You getA methods note, source table and supported findings.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Reporting
Weekly rank tracking
Produce a consistent snapshot and a meaningful change report.
BringA fixed keyword list, target URLs, market and device.
Ask Claude
For this fixed keyword list and [DOMAIN], retrieve Google ranking results for [MARKET] using a consistent device and depth. Save the date, query, returned URL, position and relevant SERP features. Compare with the supplied previous snapshot and flag changes needing investigation. Distinguish not found within the requested depth from absent everywhere. Report API cost. Save a reusable tracking specification; do not claim weekly monitoring is active unless a scheduler is actually configured.
You getA ranking snapshot, comparison and repeatable tracking spec.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Data: $0.24/mo for 100 keywords queuedWalkthrough
GA4 report on demand
Connect organic landing-page activity to real business outcomes.
BringGA4 access or an export, date ranges and an agreed conversion definition.
Ask Claude
Using connected GA4 data or the supplied export for [DOMAIN], compare the last complete 28 days with the preceding 28 days. Analyze organic landing pages, sessions and the business's defined key events. Keep property, channel, timezone, event definitions and market filters consistent. Identify where changes are concentrated, flag data-quality limits, and separate facts from possible causes. Save the underlying tables and a concise report. State the data source and exact periods.
You getA concise report plus the underlying landing-page tables.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Paid and organic overlap
Find candidates for an incrementality test.
BringAligned Search Console and Google Ads query data; analytics if available.
Ask Claude
Join the supplied Search Console and Google Ads search-term data for [DOMAIN] in [MARKET], using compatible dates and dimensions. Identify queries with paid clicks and strong organic visibility. Separate brand and non-brand queries, report conversion evidence where available, and flag unmatched or incomplete records. Produce a shortlist for incrementality testing and a proposed test design. Do not label spend wasted or recommend pausing ads solely because an organic result ranks highly.
You getAn overlap shortlist and a test proposal.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Ecommerce + local
Product listing audit
Improve listing relevance while keeping product details accurate.
BringA catalog export, product facts and the target sales channel.
Ask Claude
Review these [DOMAIN] product listings for [TOPIC] in [MARKET]. Preserve product specifications and factual claims. Use relevant keyword evidence to identify mismatched or unclear titles and descriptions, then propose edits for the 20 strongest candidates. Distinguish Google search demand from marketplace-specific behavior; do not assume they are equivalent. Export current wording, proposed wording, evidence and confidence. Flag missing product facts rather than inventing them, and report API cost.
You getA prioritized listing review with proposed titles or descriptions.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Local SERP check
See what people in the actual service area are likely to find.
BringA service, a specific location and your service area.
Ask Claude
Investigate [TOPIC] for [DOMAIN] in [MARKET] using a specific supported search location and consistent device. Retrieve live organic results and local-pack information where supported. Separate directory pages, service providers and informational pages. Compare the actual service area and supplied business information with the result types. Recommend three relevant page improvements supported by the evidence. Report location, retrieval date, coverage and API cost; avoid treating a national SERP as a local result.
You getA local competitor snapshot and three page improvements.
See example outputsample data
Illustrative mockup of what Claude hands back for vuss.io, built with sample data. Open full size
Data: $0.002 per live SERPWalkthrough
