Skip to main content
·9 min read·CMS & Platforms

Cursor AI Website Audit: Complete SEO Checklist

Built your site with Cursor AI? Use this SEO checklist to find and fix common issues with metadata, performance, accessibility, and search visibility.

Cursor is one of the fastest ways to go from idea to working website. It's an AI-powered code editor that generates entire pages, components, and layouts from plain English prompts. For solo founders, freelancers, and small business owners who want a custom site without hiring a developer, that's genuinely useful.

But speed creates blind spots. Cursor helps you build fast. It does not check whether Google can find your site, whether your pages load quickly on a phone, or whether your metadata actually describes your business. Those problems stay hidden until you wonder why nobody is visiting.

This checklist covers the most common issues we see on Cursor-built sites and tells you exactly how to check for them.

What Cursor Does Well and Where It Stops

Cursor is a code editor with AI built in. You describe what you want, like "build a landing page for a dog walking business in Austin," and it generates working code, usually React or Next.js. It can scaffold projects, write components, and handle routing.

What it does not do is optimize for search engines, write your meta descriptions, compress your images, add structured data, or test your site on a slow mobile connection. SEO, performance, and accessibility are your responsibility after the code exists.

This is not a knock on Cursor. Traditional developers skip these things too. The difference is that Cursor makes it so easy to ship that you might not realize what you skipped.

If you have also looked at other AI-built site tools, our Vercel v0 audit guide covers similar ground for that platform.

1. Check Whether Google Can Actually See Your Content

This is the single biggest issue on Cursor-built sites.

Cursor typically generates React or Next.js code. If your pages rely on client-side rendering, where JavaScript builds the page in the browser, Google may see a mostly empty page. Your site looks fine when you visit it, but search engines see a blank shell.

How to check: Open your site in Chrome, right-click anywhere, and select "View Page Source." Look for your actual content: your business name, your headings, your service descriptions. If all you see is a <div id="root"> and a bunch of <script> tags, your content is invisible to crawlers.

Browser view-source showing sparse HTML with mostly script tags and an empty div
When the raw HTML is mostly scripts and an empty shell, Google may miss the real content.

Crawlability checklist:

  • ☐ Your business name appears in the raw HTML source
  • ☐ Page headings (H1, H2) are in the HTML, not injected by JavaScript
  • ☐ Service descriptions and key content show up without JavaScript
  • ☐ You have tested with Google's URL Inspection tool in Search Console

If your content is client-rendered, you need to switch key pages to server-side rendering. In Next.js App Router, components are server-rendered by default. The problem usually comes from wrapping pages in "use client" directives or fetching all data on the client side. Google has a detailed guide on JavaScript SEO that explains what their crawler can and cannot process.

2. Fix Your Metadata

Cursor generates functional pages. It rarely generates good metadata. We see three patterns constantly:

Missing title tags. The page either has no <title> at all or uses a generic default like "Create Next App." Google uses your title tag as the clickable headline in search results. If it says "Create Next App," nobody is clicking.

Missing or placeholder meta descriptions. Either there is no description tag, or it is boilerplate from the framework. Google shows this as the snippet under your title. A missing description means Google picks random text from your page, which rarely represents your business well.

No Open Graph tags. When someone shares your link on LinkedIn, Twitter, or in a text message, OG tags control the preview image and text. Without them, shared links look bare and unprofessional.

Metadata checklist:

  • ☐ Every page has a unique <title> under 60 characters that includes your business name
  • ☐ Every page has a <meta name="description"> between 120 and 155 characters
  • ☐ Homepage has og:title, og:description, and og:image tags
  • ☐ No pages still have default framework text like "Create Next App"
  • ☐ Each page has a canonical URL pointing to itself

You can check these quickly with our meta title checker and meta description checker. For social sharing previews, use the Open Graph checker.

In Next.js, the proper way to set metadata is through the metadata export in your page or layout files. If Cursor did not generate this, you will need to add it yourself.

3. Measure Your Core Web Vitals

Cursor-generated sites often load large JavaScript bundles. The code works, but it is not optimized for speed. Google measures three metrics that directly affect your search ranking:

  • Largest Contentful Paint (LCP): How fast your main content appears. Target: under 2.5 seconds.
  • Interaction to Next Paint (INP): How fast the page responds when someone clicks or taps. Target: under 200 milliseconds.
  • Cumulative Layout Shift (CLS): How much the page layout jumps around while loading. Target: under 0.1.
Lighthouse performance report showing failing Core Web Vitals scores with red and orange indicators
Cursor can generate working code fast, but speed still needs a real audit pass.

Common problems on Cursor-built sites:

Unoptimized images. Cursor often generates <img> tags pointing to large files without specifying dimensions. This causes layout shifts and slow LCP. Use the Next.js <Image> component instead, which handles lazy loading, sizing, and format conversion automatically.

Too much client-side JavaScript. Every "use client" component ships JavaScript to the browser. If Cursor wrapped everything in client components, your bundle size balloons. Move data fetching and static content to server components wherever possible.

No font optimization. Custom fonts loaded without next/font cause a flash of unstyled text and hurt CLS.

Run our Core Web Vitals test to see where you stand. Also check your mobile performance separately, since most visitors are on phones.

For a deeper look at what these metrics mean, see Google's Web Vitals documentation.

4. Check Your Heading Structure

AI code generators tend to use headings for visual styling instead of document structure. We regularly see Cursor-built pages with multiple H1 tags, skipped heading levels (jumping from H1 to H4), or headings used purely because they make text look bigger.

Search engines use your heading hierarchy to understand what your page is about. Screen readers use it to let people navigate your content. Broken heading structure hurts both SEO and accessibility.

Heading checklist:

  • ☐ Each page has exactly one H1 tag
  • ☐ The H1 describes what the page is about, not just "Welcome" or "Home"
  • ☐ Headings follow a logical order: H1, then H2, then H3 with no skipped levels
  • ☐ Headings are not used just to make text look bigger

The W3C has clear guidelines on heading structure if you want the full picture.

5. Audit Your Images for Accessibility

This one is simple but almost always missing. Cursor generates images without meaningful alt text. You will see alt="" or alt="image" or no alt attribute at all.

Code editor showing missing alt text on multiple image tags highlighted with warning icons
Missing alt text is one of the easiest accessibility problems to fix on AI-built sites.

Alt text serves two purposes: it tells screen readers what the image shows so visually impaired users can understand your page, and it gives Google context about your images for image search and overall page relevance.

Image checklist:

  • ☐ Every meaningful image has descriptive alt text
  • ☐ Decorative images like borders or spacers use alt=""
  • ☐ Alt text describes what the image actually shows, not just "image" or "photo"
  • ☐ Images have explicit width and height attributes to prevent layout shift

Our accessibility checker flags missing and empty alt attributes across your site. The W3C images tutorial has excellent examples of good and bad alt text.

6. Add Structured Data

Structured data, also called schema markup, tells Google specific facts about your business: your name, address, hours, reviews, and services. Without it, Google has to guess, and it often guesses wrong or shows nothing.

Cursor will not generate structured data for you. You need to add JSON-LD blocks to your pages yourself.

At minimum, add:

  • ☐ LocalBusiness or Organization schema on your homepage
  • ☐ WebPage schema on key landing pages
  • ☐ BreadcrumbList if your site has navigation hierarchy
  • ☐ FAQ schema if you have a FAQ section

Use our structured data validator to check what you have and catch errors.

This is especially important for SaaS products and developer portfolios where Cursor is commonly used to build marketing sites.

7. Verify Mobile Responsiveness

Cursor generates responsive layouts most of the time, but "responsive" and "usable on mobile" are not the same thing. Watch for these common problems:

  • ☐ Text is large enough to read without zooming
  • ☐ Buttons and links have enough spacing to tap accurately
  • ☐ No horizontal scrolling on any screen size
  • ☐ Navigation menus work properly on touch devices
  • ☐ Forms are easy to fill out on a phone keyboard

Google indexes the mobile version of your site first. If your mobile experience is broken, your search rankings suffer regardless of how good the desktop version looks.

What to Do Next

Website audit dashboard with green checkmarks and red X marks across SEO checklist categories
A quick audit helps you spot the boring problems that quietly hold rankings back.

Going through this checklist manually takes time. You can catch most of these issues in about 60 seconds by running a free audit at FreeSiteAudit. It checks your metadata, performance, accessibility, and search visibility in one pass and shows you exactly what needs attention.

If you built your site with Cursor and have not audited it yet, now is a good time. The site might look great, but looking great and being findable are two different problems.

Sources

Check your website for free

Get an instant score and your top 3 critical issues in under 60 seconds.

Get Your Free Audit →