The platform you build your website on quietly decides how easily you get found. A Shopify store, a Webflow site, a Next.js app, and something you vibe-coded in Lovable all face different SEO defaults, limits, and traps. Get the platform-specific basics right and the rest of your SEO has a foundation to stand on. Get them wrong and great content never gets seen.
This guide is organised by what you built your site with. Pick your platform, fix the things it gets wrong by default, then layer on content and authority. Every section links to a deep dive.
What platform SEO means
Platform SEO is optimising for search in the context of the tool you built your site with. A website builder, a JavaScript framework, and an AI app builder each come with their own rendering model, their own controls for titles and metadata, and their own blind spots. The fundamentals of SEO do not change, but how you implement them, and what your platform makes easy or hard, very much does.
No platform ranks you on its own. What a platform does is set your ceiling: whether pages are server-rendered, how much control you have over meta tags and structured data, how fast the site loads, and whether crawlers can read your content at all. The job on this page is to clear those platform-specific hurdles so your content can compete.
The rendering problem (why AI-built sites go invisible)
The single biggest SEO issue on modern web apps is client-side rendering. Tools like Lovable, Bolt, and a lot of React setups ship a near-empty HTML file plus a JavaScript bundle that builds the page in the browser. A search or AI crawler that does not execute that JavaScript downloads a blank shell, finds no content, and has nothing to index or cite.
The test takes ten seconds: open your page, view the raw page source (not the inspector), and look for your headline and body text. If they are not there, neither Google nor an AI crawler can rely on seeing them. The fix is to render your pages on the server (SSR), generate them at build time (SSG), or add a prerender step that serves crawlers fully-formed HTML. This is the through-line across the framework and AI-builder guides below.
AI builders and vibe coding
AI builders ship fast but leave SEO switched off. Lovable, v0, Bolt, Cursor, Claude Code, Replit, and Bubble can generate a working site in an afternoon, but the output is almost always client-rendered with no real page titles, no sitemap, and no schema. The good news: these are fixable defaults, not dead ends, and fixing them is exactly where most competitors never bother.
- Lovable SEO and Bolt.new SEO cover the client-rendered React/Vite output and how to make it crawlable.
- v0 SEO works with its Next.js output and the metadata and sitemap defaults to switch on.
- Claude Code SEO and Cursor SEO are about prompting your AI assistant to build server rendering, metadata, schema, and a sitemap in from the start.
- Replit SEO covers deploying so your app is indexable, and Bubble SEO covers the meta controls in a no-code stack.
Frameworks
Frameworks give you total SEO control, which is a gift only if you use it. React, Next.js, Astro, and Angular can produce some of the fastest, best-optimised sites on the web, or some of the most invisible, depending entirely on your rendering choice and configuration. The difference between a framework site that ranks and one that does not is rarely the content. It is the setup.
- JavaScript SEO is the umbrella: how search engines process JavaScript and where it breaks.
- Single-page app SEO covers routing, prerendering, and per-route metadata for SPAs.
- React SEO, Next.js SEO, Astro SEO, and Angular SEO are the framework-specific playbooks.
Website builders
Website builders handle rendering for you, so your job is using the controls well. Shopify, Wix, Squarespace, Webflow, Framer, and WordPress all serve crawlable HTML out of the box, which removes the hardest problem. What is left is platform-specific: template duplicate content, faceted-navigation traps, meta-tag controls, schema, and site speed. These platforms can rank extremely well when set up properly.
- Shopify SEO and WordPress SEO for the two biggest ecosystems.
- Wix SEO and Squarespace SEO for the all-in-one builders.
- Webflow SEO and Framer SEO for the design-first tools.
If your SEO question is about your industry rather than your platform, the SEO by industry guides cover playbooks for SaaS, healthcare, real estate, and more.
The cross-platform SEO checklist
Whatever you built on, these are the things every platform needs to get right. The how differs by platform; the what does not.
- Crawlable content. Your headline and body text appear in the raw HTML, before JavaScript runs.
- Unique title and meta description per page. Not one default repeated site-wide.
- A sitemap.xml and a sane robots.txt that lets search and AI crawlers in.
- Clean, crawlable URLs and real links (anchor tags, not click handlers).
- Structured data (Organization, Article, Product, FAQ) so engines parse you with confidence.
- Fast loads and good Core Web Vitals, especially on mobile.
Getting cited in AI search
Every fix on this page does double duty. The same server-rendered HTML, clean structure, and schema that let Google index you are what let ChatGPT, Perplexity, and Google's AI Overviews read and cite you. If anything, AI crawlers are less forgiving: many fetch raw HTML and never run your JavaScript at all, so a client-rendered app is simply invisible to them.
That is the heart of what we build at Fokal. To understand how AI engines choose which sources to name, start with AI SEO and AI visibility tracking. And whatever your stack, schema markup is the most underused lever for both Google and AI.
Frequently asked
What is platform SEO?
Platform SEO is doing search optimisation in the context of the specific tool you built your site with, whether that is a website builder like Shopify or Wix, a framework like React or Next.js, or an AI app builder like Lovable or v0. Each platform has its own defaults, limits, and gotchas that decide how easily Google and AI engines can find you.
Why do AI-built and JavaScript sites struggle with SEO?
Most ship as client-side-rendered single-page apps. The initial HTML a crawler downloads is close to empty, and the real content only appears after JavaScript runs in a browser. Search and AI crawlers that do not fully execute that JavaScript see a blank page, so there is nothing to index or cite. The fix is server-side rendering or prerendering.
Does the platform I choose actually affect rankings?
Indirectly but significantly. No platform ranks you on its own, but each one sets your ceiling: how easily you can control titles and meta, whether pages are server-rendered, how fast the site loads, and whether you can add schema. A platform that fights those basics makes ranking harder, regardless of how good your content is.
Is Next.js or React better for SEO than a website builder?
Either can rank well when configured correctly. Frameworks like Next.js give you full control (server rendering, metadata, sitemaps) but only if you use it. Website builders like Webflow or Squarespace handle rendering for you but cap how deep you can go. The worst outcome is a powerful framework left on client-side defaults.
Can a site built with Lovable or Bolt rank on Google?
Yes, but usually not out of the box. These tools generate client-rendered apps, so you need to add server-side rendering or a prerender step, real page titles and meta descriptions, a sitemap, and structured data. Once a crawler can read the page, the same content and authority rules apply as anywhere else.
What is the single biggest SEO fix for a modern web app?
Make sure a crawler can read your content in the raw HTML, before any JavaScript runs. View the page source (not the inspector) and check your headline and body text are there. If they are missing, server-side rendering or prerendering is your highest-priority fix, ahead of everything else.
Do AI search engines see my site differently from Google?
The rendering problem is the same or worse. Many AI crawlers fetch raw HTML and do not execute JavaScript at all, so a client-rendered app is invisible to them. A server-rendered page with clear structure and schema is readable by Google, Bing, and the AI engines that increasingly sit on top of them.