You install Yoast on a Divi 5 site, open a page you spent a week building, and the SEO analysis stares back at you nearly blank. No readability score worth reading, no keyphrase feedback, a word count that says your 1,200-word landing page is basically empty. If you have searched the Divi subreddit lately, you have seen the complaints — people re-installing Yoast just to confirm that the only way to get any analysis is to abandon the builder and paste text into the default editor.
Nothing is broken. But nothing is being measured either — and if you cannot measure, you cannot audit. That gap is worth understanding before it costs you rankings.
What is actually happening
Divi 5 stores your page as structured module data — sections, rows, columns and modules serialized into block attributes. That is a good design: it is what makes Divi 5 faster than Divi 4 and what lets tools manipulate pages reliably. But an SEO plugin’s content analysis reads the editor content the way WordPress hands it over, and on a Divi page that hand-off contains almost none of your visible text. Yoast is not being lazy; it is reading a document that, from its side of the glass, barely exists.
The parts of Yoast that do not depend on reading your content keep working fine: title and meta description output, XML sitemaps, canonical URLs, schema. What you lose is the feedback loop — the readability checks, the keyphrase analysis, the internal-linking suggestions. The dashboard goes quiet exactly where a builder-heavy site needs it most.
What Google actually sees
Here is the part that should lower your blood pressure: search engines index your rendered page, not your editor. Googlebot fetches the same HTML your visitors get, Divi content included. A well-built Divi page ranks the same as a well-built anything page.
The real risk is not invisibility. It is flying blind. When no tool is reading your pages, the ordinary mistakes stop getting flagged: a page with 150 words of real text, a “heading” that is actually a bold paragraph styled to 32px, a missing meta description on the page that matters most, an orphan page no other page links to. On a ten-page site you might catch these by hand. On a fifty-page client site, you will not.
How to audit Divi SEO by hand
If you want to do this manually, here is the checklist that covers most of what an SEO plugin would have told you:
- Headings: open the page, view source, and check that your section titles are real
h2/h3elements — not Text modules styled to look like headings. Screen readers and search engines only see the tag. - Titles and metas: every indexable page needs a title that uses its ~60 characters and a meta description of 70–160. “Privacy Policy” as a full title wastes the most valuable line in the search result.
- Thin pages: anything informational under ~300 readable words is unlikely to outrank a page that actually answers the question.
- Internal links: every page should link somewhere, and your money pages should be linked to. Orphans do not get crawled often and do not accumulate relevance.
- Slugs and staleness: short descriptive URLs, and a date-check on anything that claims to be current.
Or let something read the builder itself
This problem is half of why we built site-wide audits into Divi Autopilot. The SEO audit does not wait for WordPress to hand it editor content — it reads the stored Divi markup module by module, every page in one run. It checks title length, missing meta descriptions (it reads Yoast’s fields and respects them), fake headings with the exact module path so you can fix the right one, thin content, internal links and broken ones, noindex flags, slug quality. If you have recorded a focus keyphrase in Yoast, it checks the page is actually built around it.
Then the fixer closes the loop on the mechanical part: it can derive a meta description from the page’s own opening text into Yoast’s field — journaled, and individually undoable if you would rather write your own.
One honest note from our own kitchen: the posts on this blog are written in the plain WordPress editor, not the builder — prose belongs in the editor, layout belongs in Divi, and Yoast reads these posts perfectly. The pages of this site are Divi 5, audited by the plugin they sell. That is the arrangement we would recommend to anyone.
Try it on your own site: 43 of Divi Autopilot’s 86 tools are free forever, including the audits that produced everything in this post. See how it works →