What Dynamic SEO is
A control plane for the SEO signals your pages send: edited in one place, injected server-side at the edge, and visible to every crawler without a deploy.
Most sites keep their SEO where they keep everything else — in the template, in the CMS, in the code. That works until the number of pages outgrows the number of people willing to edit them. Changing one title pattern across ten thousand product pages becomes a migration. Adding structured data becomes a release.
Dynamic SEO separates the two. The signals a page sends to search engines are edited here, and delivered to your live site without touching the site itself.
What actually changes on your site
Your pages keep rendering the way they already do. What changes is the <head>:
title, meta description, canonical, robots directives, Open Graph and Twitter
tags, and JSON-LD structured data. Those are injected server-side by your
integration, before the HTML reaches whoever asked for it.
Server-side matters here. A crawler that does not execute JavaScript sees the
same finished <head> as a browser that does. Nothing depends on the client
running anything.
What it is not
It is not dynamic rendering. Dynamic rendering means serving one version of a page to crawlers and a different one to people. That is a different technique with a different risk profile. Dynamic SEO injects the same content for everyone, before the response leaves the server — there is no crawler-only variant.
It is not a reporting tool. The audit, the score and the Search Console figures exist to tell you what to change. The point of the product is that you can then change it.
It is not a page builder. Your content, layout and routing stay yours. Only the head is ours.
How the pieces fit
Four things happen, in order, and each has its own page in the app:
- Discovery collects the URLs your site has.
- Crawling fetches the mapped ones and records what they currently carry.
- The audit scores that against the checks we run, and tells you where the gaps are.
- Publishing writes your intended metadata, and your integration serves it.
How it works walks through that chain in detail. If you have just created an account, Getting started is the shorter path.
What you need for it to work
One thing: an integration installed on your site, so there is something to receive the published SEO and put it in the response. Until then, everything in the app is analysis — accurate, but not yet delivered. The Deploy view is where you confirm that delivery is actually happening, URL by URL.
Read next
How it works