SEO for sites built with Cursor
Cursor makes you fast. You describe the site, the agent writes it, you ship the same week. The catch: an AI editor optimises for what you asked for, and almost nobody asks for SEO. The result is a wave of genuinely good products sitting on page nine of Google with zero presence in ChatGPT answers.
The failure mode of editor-built sites
Unlike site builders, Cursor gives you whatever stack you asked for: Next.js, Vite, Astro, plain HTML. That freedom means there is no default SEO safety net at all. Three patterns show up constantly in Cursor-built sites:
1. Placeholder metadata. Titles like "My App" or the framework's starter default, empty descriptions, no Open Graph tags. Every search result and shared link looks broken before anyone clicks.
2. Client-only rendering. If the agent scaffolded a single-page app, your content is invisible to AI crawlers like GPTBot and PerplexityBot, which do not execute JavaScript, and slower to index on Google.
3. Missing infrastructure. No sitemap.xml, no robots.txt, no canonical tags, no structured data. Individually small, together they are the difference between rankable and invisible.
The fix, in Cursor's own language
The nice thing about a Cursor site is that fixing it is also promptable. The hard part is knowing what to prompt: which pages are missing descriptions, which tags conflict, what the canonical should be, what structured data your product page deserves. That diagnosis is exactly what an audit is for.
- Run a scan that reads your site the way crawlers do, not the way your browser does
- Fix titles and meta descriptions around real search intent
- Add sitemap.xml, robots.txt and llms.txt
- Make sure content is server-rendered or pre-rendered
- Add canonical tags and JSON-LD structured data
- Re-scan to verify every fix actually shipped
Where Drazen fits
Drazen is the agent on the other side of the shipping line: it audits the live site, writes each fix as real code, and opens a pull request on your repo. You review it in GitHub like any other PR, merge, done. Prefer to keep everything inside your editor? Drazen writes the exact fix prompt to paste into Cursor, then re-scans to confirm it worked. Either way you never write the SEO code yourself, and Drazen keeps monitoring the site afterwards so a refactor cannot quietly undo it.
Questions
I already asked Cursor to 'add SEO'. Is that enough?
Usually not. Without an audit of the live site, the agent guesses: it may add generic tags while missing the actual blockers, like client-only rendering, duplicate canonicals or an unreadable robots.txt. Fix what a scan proves is broken, then verify with a re-scan.
Does Drazen conflict with changes I make in Cursor?
No. Drazen ships fixes as pull requests, so nothing lands without your review. If a later Cursor session overwrites a fix, Drazen detects it on the next scan and writes it again.
What does it cost?
The audit is free and takes about 30 seconds. Fixing everything is $99, once, per site. The optional watchdog that keeps it fixed is $12 a month, first month free.
See what your site scores
Drazen scans your site the way Google and ChatGPT see it, shows you everything that is hurting you, and writes the fixes itself. Free, about 30 seconds.
Run the free scan →