Changelog

What changed for you as a user of the app or the plugin, newest first. Rebuilds you cannot see are not listed.

September 29, 2026App
The status surfaces say what your site is doing
The verify step on the Integrate page now says what your own site has done: whether it has called the edge, how many calls the last day got content, and when it was last seen. The connection test asks the edge for your newest published page instead of the homepage, and says which page it asked for.

The integrations card sees a Next.js site, and a site is recognised as Next.js from the headers it sends, from its next crawl on. The deploy view no longer counts a page's failures from before it was published, and "Missing H1" now says what it means: no H1 in the published content.

The Next.js package (2.2.1) writes the same marker on the generateMetadata path as the head component, so "is Dynamic SEO serving this page" has one answer.
September 29, 2026App
The performance page says when it is fetching
While Search Console data is being fetched, the performance page says so, with the number of days left, instead of showing an empty state that asks you to click Refresh once more. The page updates on its own once the data is in.

When the fetch is complete and Google still has no impressions for the site, it says that. That is common for a new site and not a fault.
September 29, 2026App
One matcher for patterns, and the edge deploys itself
A pattern category now matches the same way everywhere: the live count in the editor, the save, and the rules applied to newly discovered pages all run one matcher. A pattern fits when it matches the page's path or the whole address, so a regex written for the path captures what the label promised. The category counts refresh right after a save instead of up to 90 seconds later.

The edge worker is deployed by CI on every change to it, after its tests, so what is merged is what serves.
September 29, 2026App
The Next.js integration is a download
The Integrate page has a Next.js guide, and its first step is a download, the same way the WordPress plugin is. The package was only ever installable from inside our own repository; now any App Router site can commit the tarball and install it from that path. The guide's six steps fill in your domain and the start of your site key, and its last step verifies the connection.

The Delivery card names a Next.js site as one. Until now the edge did not recognise the package's requests, so a Next.js site showed "Integration" without a platform or a version.
September 29, 2026App
The Next.js guide after its first customer run
A Next.js site on Cache Components could not follow the guide: the head component fails the build there. The guide, the package README and a new public Next.js guide in the docs now show the second path, through each page's own metadata, and say which steps belong to which path.

The connection test no longer reports an error when nothing is published yet. It says that the key works and the edge answers, and it says plainly when the edge rejects the key.

A Next.js site is now detected as one from its own headers and assets, so the Integrate page opens the right guide. The package download includes its README again, and the package no longer drags Babel into every install: only the next.config wrapper needs it.
September 29, 2026App
The groups in the score breakdown open up
Every group under a pillar, such as Media or Meta tags, now opens. Inside are the checks the group is made of, how many pages each check flags, and a link to exactly those pages in the URL view. Hovering a group's name says what it measures, both in the score breakdown and in the list of why the score isn't 100, where the name also leads to the pages.

The help panel no longer writes "Show on page" under every row. The offer sits as a small mark at the row's edge. A new help entry lists the groups and their checks, so a search for "media" finds an answer.

The work log shows a category's name rather than its internal key when a page has been mapped to a category.
September 29, 2026App
Delivery and the next step on the dashboard
The dashboard now shows whether the site is actually getting the content: which integration last called in, how many pages are published, and how many of the last day's calls got content, errors included. A WordPress site on an older plugin version sees that a newer one exists.

The Next step card follows where the site is in its setup: categories, template, publishing, integration. Only once all of that exists does it point at the audit finding that gives the most points back.
September 20, 2026Documentation
A documentation page for the WordPress plugin
The plugin has its own page in the documentation: installation, the site key, the wp-config constants, how Yoast and Rank Math are handled, and a checklist for when nothing changes on a page.

Read The WordPress plugin.
September 14, 2026App
The URL view searches one thing at a time
The search field on the URL page has a mode: URL or Content. A row used to match on its address, its title or a word in its body all at once, so the list could not be explained from the field. Rows for addresses like /?p=1 now show their query instead of appearing as /.
September 5, 2026App
System pages can be excluded in one click
A WordPress site arrives with wp-admin, feeds, ?p= links and tracking duplicates in its crawl, scored as pages and listed as "missing title". The URL view now opens with a card grouping them: admin, api, feeds, checkout, search, WordPress ID links, tracking parameters and files. One click excludes them, and every count in the app reads the same definition of which pages count. Three numbers in the Overview that were wrong for three different reasons are fixed.
September 3, 2026App
A format on the variable, and two new rule conditions
A format, such as how a date is written, is set on the variable and applies everywhere it is used: in the preview, in the insert panel and in the published title. Rules can now use two conditions that existed in the engine but were missing from the menu: the query string contains a value, and a date falls in a range.
September 2, 2026App
Variables: one grammar, and a suggestion from the site's own fields
The variables page says the same thing everywhere: Your own, From your site and Rule. The list is grouped by the question you are asking, suggestions from the crawl have a single place to be approved, and a new site is offered a title suggestion built from its pages' own fields instead of an empty box. At the top, the template is shown on three real pages from the site.
August 26, 2026App
A refusal is not a broken link
The link analysis did not distinguish "the page is gone" from "the server declined to answer". A site whose host answered 508 to 62 of 262 requests showed 1,859 broken links and had one. Now only real errors count as broken, and a refusal is shown as a refusal.
August 26, 2026App
Help in the app, and documentation that explains why
The help panel is on every page and describes the page you are on. The documentation on dynamicseo.com answers what the panel cannot: what the product is, how discovery, categories, crawling and publishing fit together, and how the score is computed.

Read the documentation.
August 22, 2026App
A new site discovers, crawls and says so
A newly added site could sit uncrawled with no explanation. Now it is discovered, crawled and shows what is happening in the Overview. Keywords, Integrate and Visualize are reachable from the menu on every page.
August 18, 2026App
Robots is a field you choose
The robots directive used to be published with whatever value the crawl happened to see on the page, so a site's own noindex could come along and be served by us. Now robots is published only when you set it, per URL, and a published correction is recomputed immediately instead of after the next crawl.
August 15, 2026App
Keywords built around the conflict
The keywords view starts from conflicts: phrases that two or more pages target. With Search Console connected, conflicts Google has actually measured are marked apart from the ones we inferred from page content. Shared words, translations and your own brand name no longer count as conflicts. The list handles thousands of rows without slowing down.
August 5, 2026App
One word for each variable type, and no publishing with unresolved tokens
The same thing had eight names on the variables page. Now the three types are called the same thing in tabs, lists, filters and badges. A template with a token that cannot be resolved can no longer be published.
July 19, 2026App
URL Inspection from Search Console
The Performance view shows per URL what Google says about indexing and which canonical Google chose, compared with the one you published. When the account has several properties, the domain property is preferred.
July 8, 2026WordPress plugin 4.5.3
One field at a time, and the crawler sees the original
The plugin takes over one field at a time: only the fields you published are replaced, the rest is left to Yoast or Rank Math, so a social image you set there stays (4.5.1). Rank Math's advanced robots tag is silenced when Dynamic SEO delivers the directive, so the page gets one robots tag instead of two (4.5.2). The crawler always sees the site's original page, never the injected output, so a title template cannot stack on itself at the next publish (4.5.3).
July 2, 2026WordPress plugin 4.5.0
Test connection, www sites and a five-minute cache
The Test connection button under Settings → Dynamic SEO says whether content is being served, not yet published, or the key was rejected. Sites with www in their address match their registered domain. A canonical pointing off the site is dropped instead of risking de-indexing. The plugin's own cache is five minutes, so a missed purge heals itself.
July 2, 2026App
Publishes go live immediately
Every cache layer is cleared when you publish: in the plugin, in our API and in our own cache, and the new version is warmed so the first request hits the cache. A page could previously serve the old version for up to an hour.
June 30, 2026App
Import SEO fields and categories from CSV
Under Content you can import a CSV. Rows are matched to crawled URLs, fill the SEO fields and group the pages into categories. A preview shows what would change before anything is written, and you choose whether the file completes or replaces what is there.
June 27, 2026App
Visualize: the schema as a constellation
The site's structured data is drawn as a radial graph around the page, with a side panel that is always there, even while the view is loading or empty.
June 8, 2026App
Categories are edited right on the URL table
The three ways to define a category, URL pattern, page content and hand-pick, share one editor next to the URL table. Hand-pick works end to end: ticked rows are assigned when you save. Search the pages' content and capture the matches as a category.
June 1, 2026App
Structured data: connections you declare yourself
How blocks connect is your decision, not a guess in the background. The builder lets you pick blocks freely and say how they connect; the engine only writes the references. Fields with unfilled placeholders are left out instead of being published with the braces still in.
April 22, 2026App
Discovered URLs can be reviewed before they count
A site can be put in review mode: new URLs the crawler finds land in an inbox instead of straight in the overview. Filter rules can include or exclude, and excluded pages are hidden automatically.