SEO for Converted WordPress Themes

Evergreen SEO guide for AI-to-WordPress conversions — titles, meta tags, JSON-LD, redirects, and plugin strategy after WPConvert.

Converted WordPress themes from AI builders and static exports behave differently from classic blog-driven sites. Page markup often lives in PHP templates, not in the post body field. SEO still works — but you need a strategy that matches how WPConvert themes are structured.

This guide is the canonical reference for organic search after conversion. For Yoast and Rank Math plugin setup, see the companion Yoast & Rank Math setup guide.

How WPConvert themes handle SEO out of the box

Every WPConvert theme ships with captured metadata from your source export:

• Page titles and meta descriptions per route
• Open Graph and Twitter Card tags
• Canonical URLs on public pages
• JSON-LD structured data (Organization, WebSite, WebPage, and more where detected)

These assets live in assets/data/seo.json and assets/data/seo-content.json inside your theme. The theme outputs tags on the front end even before you install an SEO plugin.

That means your live site can be indexable on day one. Admin SEO scores are a separate problem — plugins analyse post_content by default, which is why we publish a dedicated Yoast/Rank Math guide.

Pre-conversion SEO you control in the builder

The best SEO outcomes start before upload. In your AI builder or static project:

• Use one H1 per page with a clear primary topic
• Write unique title tags and meta descriptions per route (not one global default)
• Add meaningful alt text on images that matter for search
• Prefer real links (<a href>) over JavaScript-only navigation so crawlers see your site graph
• Keep tab panels, FAQs, and carousels in the DOM (hidden with CSS) so content survives conversion

See optimize before conversion for the full export checklist.

URL structure and redirects after launch

When you move from a builder subdomain to your own domain:

1. Map every old URL to a WordPress equivalent before DNS cutover
2. Implement 301 redirects in WordPress (Redirection plugin, Rank Math, or server rules)
3. Update Google Search Console property to the new domain
4. Submit an updated sitemap after launch

WPConvert preserves path slugs when your export uses clean routes. Single-page apps with hash-only navigation may need manual URL planning — document anchors and target pages in your migration checklist.

Structured data strategy

WPConvert emits JSON-LD based on what it can infer from the export:

After launch, validate with Google Rich Results Test. If you add WooCommerce, product schema comes from WooCommerce and your SEO plugin — not from the base theme alone.

Do not duplicate JSON-LD blocks. When Yoast or Rank Math is active, WPConvert themes stand down overlapping meta output to avoid duplicate tags.

Sitemaps and indexing

On WordPress:

• Enable XML sitemaps (WordPress core since 5.5, or via Yoast/Rank Math)
• Exclude staging environments from indexing (noindex on dev URLs)
• Block thin or duplicate routes (preview URLs, attachment pages you do not use)

WPConvert.ai publishes its own marketing sitemap at wpconvert.ai/sitemap.xml. Your converted site needs its own sitemap on your domain — generated by WordPress after install.

Content editing and SEO over time

Converted themes are template-driven. Editors update copy in WordPress pages or the block editor depending on how sections were mapped. For SEO maintenance:

• Revisit title and description when you rewrite hero copy
• Use your SEO plugin to track focus keyphrases per landing page
• Refresh internal links when you add new service pages or blog posts
• Monitor Core Web Vitals — heavy animation scripts from AI exports may need cleanup post-launch

Agencies should document which sections are template-locked vs editable so clients do not break layout when chasing SEO tweaks.

Local SEO and multi-location sites

If your builder site included location pages:

• Recreate location entities as WordPress pages or custom post types
• Add LocalBusiness schema via your SEO plugin where appropriate
• Keep NAP (name, address, phone) consistent in footer templates

WPConvert does not auto-generate LocalBusiness schema unless it was present in source markup — plan plugin configuration after conversion.

International and multilingual SEO

Export a single language from your builder for the cleanest first conversion. Add multilingual plugins (WPML, Polylang, TranslatePress) after the theme is stable:

• Configure hreflang in your multilingual plugin
• Translate slug strategy before publishing secondary languages
• Avoid machine-translating template PHP — translate through WordPress workflows

Measuring success

Track these within 30 days of launch:

• Indexed pages in Search Console
• Impressions and clicks for branded vs non-branded queries
• 404 errors after redirect map
• Average position on your top 5 money pages

Compare staging vs production before cutover so you know the theme renders the same for Googlebot as for users.

Core Web Vitals on converted themes

AI exports often ship large JavaScript bundles and scroll animations. After conversion:

• Defer or remove unused animation libraries on marketing pages
• Compress hero images (WebP where supported)
• Enable host-level caching (object cache + page cache)
• Test mobile LCP on real devices, not only desktop Lighthouse

Poor vitals hurt rankings; they are fixable post-launch without re-converting.

Blog vs pages SEO after conversion

Many builder sites mix landing pages and a blog. In WordPress:

• Assign clear URL prefixes (/blog/ for posts is conventional)
• Set one focus keyphrase per money page in your SEO plugin
• Use internal links from blog posts to service pages (and vice versa)
• Avoid duplicating the same H1 on a page and a post

WPConvert maps routes from your export — rename slugs in WordPress before you accumulate backlinks.

Common mistakes after conversion

These issues show up repeatedly on converted themes. Catch them before you announce the new domain:

• Installing Yoast or Rank Math without reading the companion guide — duplicate title tags and JSON-LD when theme output and plugin output overlap. Follow Yoast & Rank Math setup for converted themes before activating scoring workflows.
• Leaving staging indexable — dev subdomains get crawled and compete with production. Apply noindex on staging and block crawlers at the host level.
• Skipping the redirect map — every builder URL, preview path, and old blog slug needs a 301. Missing redirects are the top cause of post-migration traffic drops.
• Treating SEO plugin scores as launch blockers — green bullets in admin often require copy in post_content, which template-driven pages may not use. Validate live HTML source and Search Console instead.
• Publishing attachment and thin pages — WordPress auto-creates attachment URLs and sometimes empty archives. Exclude or noindex what you do not intend to rank.
• Ignoring JavaScript-only nav from the export — if primary links never became <a href>, crawlers see a shallow site graph. Fix in the builder and reconvert, or patch templates before link-building.

Post-conversion SEO QA checklist

Run this on production (or staging that mirrors production) within 48 hours of theme activation:

On-page

• View source on homepage and top 5 money pages — confirm one <title>, one meta description, one canonical per page
• Exactly one H1 per page; heading hierarchy does not skip levels
• Open Graph and Twitter Card tags render with correct absolute URLs
• No duplicate JSON-LD blocks (validate with Rich Results Test)
• Images that matter for search have descriptive alt attributes

Technical

• XML sitemap loads at /wp-sitemap.xml or plugin URL; submit in Search Console
• robots.txt allows crawling of public pages; staging is blocked or noindexed
• HTTPS everywhere; no mixed-content warnings in browser console
• 301 redirect table tested for old builder URLs and www/non-www preference
• Mobile-friendly test passes on hero and primary CTA sections

Ongoing

• Search Console property verified for production domain
• Core Web Vitals spot-check on mobile (LCP, CLS)
• Internal links from nav, footer, and blog posts point to live slugs — not builder placeholders

Document results in your client handoff so the next editor knows what was verified.

Agency workflow notes

Agencies shipping converted themes for clients should standardize SEO handoff:

1. Pre-sale — Confirm whether the client needs local SEO, multilingual, or WooCommerce schema. Scope plugin work separately from theme conversion.
2. Pre-conversion — Run the optimize before conversion checklist in the builder repo; export a single language.
3. Staging — Activate theme on staging with noindex, install one SEO plugin, configure per the Yoast/Rank Math guide, and complete the QA checklist above.
4. Redirect package — Deliver a spreadsheet: old URL, new URL, redirect type, implemented (Y/N). Client IT or your team implements before DNS.
5. Cutover — Lower TTL 24–48 hours before; switch DNS; verify SSL and redirects; submit sitemap same day.
6. Handoff — Document which pages are template-locked vs block-editable, where seo.json lives, and who owns Search Console. Link to guides for post-launch maintenance.

Keep a builder reference (Lovable, Framer, Cursor, etc.) in the project folder — see builders for per-platform export notes when you need to reconvert after SEO-related markup fixes.

Troubleshooting

If rankings stall after technical fixes, revisit on-page quality and internal linking — conversion preserves structure, not a content strategy.