Using Linkilo with Divi

How Divi content gets scanned

Unlike Elementor, Divi keeps the page text inside the normal post_content field — wrapped in Divi shortcodes like [et_pb_section] and [et_pb_text]. Linkilo:

1. Reads post_content as usual.
2. Strips the Divi shortcodes during scanning so the keyword extractor sees clean text.
3. Re-inserts the shortcodes when it writes a link back, preserving your layout.

The presence of a _et_pb_use_builder postmeta value tells Linkilo "this page is built with Divi." That just changes how Linkilo timing-coordinates its save with Divi's save — see below.

The Divi save-order issue (and how Linkilo handles it)

Divi has its own front-end builder save process that fires on et_fb_ajax_save_verification_result. When you click Update in Divi's builder, both Divi and any plugin that touches post_content are racing to write to the same database row.

Without coordination, you get this scenario:

1. You click Update in Divi.
2. Linkilo writes a suggested link into post_content.
3. Divi finishes its own save and overwrites post_content — wiping the link Linkilo just added.

Linkilo registers a filter on et_fb_ajax_save_verification_result (Feed::verify_divi_save_status) that waits for Divi's save to complete first, then runs the link insertion. The link survives.

You don't have to configure anything — this protection is automatic whenever Divi is detected.

Where the suggestion panel appears

Same approach as Elementor: Divi's visual builder is its own UI surface and doesn't accept third-party metaboxes inside the builder canvas.

To see Linkilo's suggestions for a Divi page:

1. From the WordPress admin, click Edit (default editor) rather than Edit with the Divi Builder.
2. The standard WordPress edit screen loads with the post content as Divi shortcodes.
3. Scroll down — the AI Link Suggestions metabox is below the content area.
4. Approve, reject, or customise suggestions as usual.

When you switch back to the Divi Builder, the links Linkilo added are already in the text widgets.

How "Apply" works on a Divi page

When you apply a suggestion:

1. Linkilo finds the source sentence in the rendered text of a [et_pb_text] (or similar) shortcode.
2. Wraps the anchor with an <a> tag.
3. Writes the modified shortcode back into post_content.

If Divi's builder is currently open in another browser tab, Linkilo's coordination filter makes sure the Divi save fires first, then Linkilo's. Otherwise the standard insertion path is used.

Troubleshooting

My link disappeared after I edited the page in Divi

You likely hit the save-race scenario and the coordination filter didn't catch it (rare, but possible if a third plugin is also touching post_content). Re-apply the suggestion from AI Suggestions, then don't re-edit the page in Divi's builder for a few seconds while the save completes.

Linkilo doesn't see my Divi page

Confirm the page actually has Divi content (_et_pb_use_builder should be set on the post). New blank pages without any Divi modules have nothing for Linkilo to scan.

A suggestion has the wrong "section" context

Linkilo identifies the surrounding sentence to pick a healthy insertion point. With Divi, that sentence may span what looks like multiple modules in the visual builder but is actually one [et_pb_text] block in source. If a suggestion lands somewhere strange in the visual layout, use Customize Anchor to choose a different anchor inside the same module.

See also

• Using Linkilo with Elementor
• Using Linkilo with Gutenberg
• Using Linkilo with the Classic Editor
• Does it work with page builders? (overview)