Generated Pages Show Outdated Content After Updates

This guide helps you fix situations where MPG-generated pages still show old content after you have updated your source file and clicked Fetch and use.

If your project uses Live refresh

If your project is set to Live sync and your generated pages still show older values after a source update, MPG may still be rebuilding its data index when a visitor opens the page. In that short window, the frontend can load stale content from the previous index.

Use the steps below to switch to a scheduled sync, rebuild MPG's table/index data, and then retest the affected URLs.

Switch Live refresh to a scheduled interval

1. In your WordPress dashboard, go to MPG > All Projects and open the affected project.
2. In Main > Step 1: Select source, find Sync frequency.
3. Change Live to the nearest non-Live option available in your UI, such as 15 minutes, 30 minutes, Hourly, or On Demand.
4. Save or update the project.
5. Click Fetch and use to pull the latest source data again.

⚠️ Important: If your MPG version does not show 15-minute or 30-minute intervals, choose any available scheduled option (for example Hourly or On Demand) instead of Live.

Rebuild the MPG table/index manually

1. In your WordPress dashboard, go to MPG > Advanced settings.
2. In Update tables structure, click Update.
3. Wait for the process to complete, then open your MPG project and run Fetch and use one more time.

This forces MPG to refresh its internal tables/index data and helps when stale content appears right after project or source changes.

Clear caches and retest generated URLs

1. Save your WordPress permalink settings by going to Settings > Permalinks and clicking Save Changes (no permalink edits required).
2. Clear all cache layers you use: caching plugins, server/hosting cache, CDN cache, and your browser cache.
3. Open one of the affected generated URLs in a private/incognito window and verify the latest values are now visible.
4. If needed, test a second affected URL to confirm the refresh is consistent across pages.

Step 1: Adjust Page Builders Compatibility

The most common cause of stale content on generated pages is a mismatch between MPG's rendering mode and the page builder or theme active on your site. Different plugin combinations require different compatibility settings.

1. In your WordPress dashboard, go to Multiple Pages Generator > Advanced Settings.
2. Locate the Page Builders Compatibility option.
3. Try each available option one at a time, saving between attempts.
4. After changing the option, visit one of the affected generated pages to see whether the content has updated.

💡 Tip: There is no single correct value for Page Builders Compatibility — the right setting depends on which themes and plugins are active on your site. Work through the options systematically until the pages display the correct content.

Step 2: Purge Server-Level Cache

Even after clicking Fetch and use, a server-level caching layer (such as LiteSpeed Cache, Nginx FastCGI Cache, or a hosting control panel cache) may continue serving a cached version of the page, making it appear as though the content has not changed.

1. Log in to your hosting control panel or caching plugin settings.
2. Perform a full cache purge or flush for your site.
3. If your host provides a Purge All or Clear Cache button in the dashboard, use it.
4. After purging, visit the affected generated pages directly in a browser to confirm they now show the updated content.

📝 Note: Plugin-level caches (for example, WP Rocket or W3 Total Cache) are separate from server-level caches. Purge both if you are unsure which layer is responsible.

Step 3: Validate Your CSV Headers

Certain column header names in your source file can cause MPG to fail silently when processing updates.

• Do not use url as a column header. MPG reserves this name internally, and using it can prevent content from being processed correctly.
• Avoid spaces and underscores (_) in header names. Use hyphens (-) or camelCase instead.
• Do not wrap headers in brackets such as {{title}} or [[title]]. Plain header names are required — MPG adds the mpg_ prefix automatically.

After correcting your headers, re-upload or re-link the source file and click Fetch and use again.

Step 4: Check for theme-builder or global template overrides

Some theme builders can apply a global/default page template that overrides the normal page content output. When this happens, MPG can refresh correctly in the background, but generated URLs may still show an older or static layout from the theme template.

If you already tested Page Builders Compatibility in Step 1, keep in mind that compatibility hook/priority changes do not override an intentional global template assignment.

YOOtheme Builder: MPG source page assigned as the default page template

If the MPG source/template page is set as the default/global page template in YOOtheme Builder, generated pages can inherit that fixed template instead of showing newly added MPG sections.

To fix this, use one of these options:

1. Add the missing section directly inside the YOOtheme default template if that content should appear on all affected pages.
2. Create or assign a dedicated custom YOOtheme page template for the MPG project so generated pages can render their own MPG template content.

How to verify the fix

After changing the template assignment:

1. Clear YOOtheme/theme cache (if enabled).
2. Clear your site/server cache and any CDN cache in use.
3. Open an affected generated URL in a private/incognito window.
4. Confirm the newly added MPG section now appears on the frontend.

Still Seeing Outdated Content?

If the content still appears stale after completing all steps above:

• Disable any third-party optimization or minification plugins temporarily and test again.
• Check whether your theme or page builder has its own built-in caching or fragment caching, and clear it.
• If you recently changed the URL slug for a generated page, the old cached URL may still be served. Allow the cache TTL to expire or force a purge.

📝 Note: If you still need help, feel free to contact our support team — pro users / free users.