Integrations

An integration is the piece that lives on your side. It is what turns everything Dynamic SEO knows about a URL into something a search engine actually sees.

What it does

When a request arrives at one of your pages, the integration asks us for the SEO belonging to that URL and puts it into the response before it is sent.

That is the whole mechanism. It matters because of where it happens: the metadata is in the HTML when the page leaves your server, rather than being added by JavaScript afterwards. See what Dynamic SEO is for why that distinction is the point of the product.

It also means the integration is the only part of the chain we cannot see directly. Everything the Deploy view reports is something your integration told us.

The API key

The key identifies your site to us. Each site has its own, and every integration for that site uses it.

Regenerating a key is not a small action: it stops every existing integration for that site until each one is updated with the new key. If you have one install, that is a minute of downtime you control. If you have several, update them all before regenerating, not after.

Verify before you believe it

The last step of every guide checks that your site answers correctly. It is not a formality — nothing is served until it succeeds.

A guide you followed but never verified is indistinguishable, from our side, from one you never started.

Detected is not connected

The Integrate view can show a platform as Detected. That means either the last crawl recognised the platform your site runs on, or an integration has reported in at some point.

Neither is a claim that the connection currently works. Detection reads fingerprints in your HTML; a site can be very obviously WordPress with nothing installed at all. Treat Detected as a suggestion about which guide to open, and the verify step as the answer to whether it works.

What you can install today

WordPress is installable now. The plugin is a download, it carries the whole flow — install, key, configure, verify — and it is the path we recommend.

Every other platform in the list is marked Not available yet, and shows a notice instead of steps. That is deliberate. Their guides begin by installing a package that has not been published, so rendering the steps would hand you a command that cannot succeed and a failure that looks like your mistake.

The guides are written and waiting. Each one appears in place of its notice on the day its package ships.

Where to look when nothing arrives

Work backwards along the chain, because each step is invisible until the one before it is done:

1. Is anything published? Generated content is not published content.
2. Has the integration verified? Re-run the verify step.
3. Is the key current? A regenerated key breaks installs silently.
4. Has any traffic arrived? A page nobody requested reports nothing.

The Deploy view distinguishes the last two clearly: an Error row means your integration tried and failed, while an Idle row means it was never asked.