Getmd works with any publicly accessible website, but the four platforms we see most often – WordPress, HubSpot Content Hub, Shopify, and Webflow – each have their own characteristics that affect how AI readability works in practice. Understanding these differences helps you get the most out of Getmd from day one.
This guide covers what Getmd does with each CMS, what to expect from the conversion, and any platform-specific considerations you should know about.
WordPress
WordPress powers roughly 43% of the web, and it’s the CMS we see most often across Getmd customers. It’s also the CMS with the most variability in HTML structure, because themes and page builders can radically change how content is structured.
How Getmd handles WordPress
Standard themes (Astra, GeneratePress, Kadence, Twenty Twenty-Four, and similar) use relatively clean HTML with content wrapped in recognisable containers like <article>, <div class="entry-content">, or <main>. Getmd identifies these containers and extracts the content cleanly, stripping the theme’s header, footer, sidebar, and widget areas.
Page builder output (Elementor, Divi, Beaver Builder, WPBakery) is more challenging. These tools generate deeply nested HTML with dozens of wrapper <div> elements, custom class names, and content distributed across multiple containers. Getmd’s extraction engine handles the common page builders, but if you’re using a particularly unusual layout structure, you may see some extra formatting in the output initially.
Gutenberg blocks are generally clean. WordPress’s native block editor produces semantic HTML that converts well to markdown. Custom blocks vary – standard paragraph, heading, list, image, and table blocks convert cleanly. Highly specialised custom blocks (interactive widgets, embedded applications) may need attention.
WordPress-specific considerations
Plugin interference. Some WordPress security plugins (Wordfence, Sucuri, iThemes Security) add bot-blocking rules that can interfere with AI crawlers and Getmd’s conversion requests. If you see unexpected 403 errors in your analytics, check your security plugin settings for bot-blocking rules.
Caching plugins. WordPress caching plugins (WP Super Cache, W3 Total Cache, WP Rocket) cache your HTML output, which is what Getmd fetches. This is fine – Getmd converts whatever HTML your server returns, cached or not. But if your caching plugin is serving very stale pages, Getmd’s markdown will reflect that stale content. Make sure your WordPress cache is reasonably fresh.
REST API. WordPress has a built-in REST API that returns structured JSON content. Getmd uses the HTML output rather than the REST API because the rendered HTML is what actually represents your live site – including theme modifications, shortcode output, and page builder layouts. The REST API returns raw content that often doesn’t match what visitors see.
HubSpot Content Hub
HubSpot Content Hub (formerly HubSpot CMS) is the second most common CMS we see, particularly among B2B companies and agencies. Its module-based architecture creates specific conversion challenges and opportunities.
How Getmd handles HubSpot
Module-based pages. HubSpot pages are composed of drag-and-drop modules – rich text modules, CTA modules, form modules, custom modules. The page content isn’t in a single HTML container; it’s distributed across multiple module containers interspersed with layout and functional modules.
Getmd identifies HubSpot’s module structure and extracts content from rich text modules while filtering out CTA modules, form modules, navigation modules, and other functional elements that aren’t page content. The result is the textual content of the page without the interactive components.
Blog posts on HubSpot are more straightforward. The blog post body is typically in a single container, and Getmd extracts it cleanly along with the post title, featured image, and publication date.
Landing pages are the most variable. HubSpot landing pages often use heavily customised module layouts with minimal text and lots of visual elements (images, icons, animations). The markdown conversion of a landing page may be sparser than you expect because much of the page’s “content” is visual rather than textual.
HubSpot-specific considerations
HubSpot’s CDN layer. HubSpot serves pages through its own CDN with specific caching behaviour. Getmd works through this layer without issues, but be aware that HubSpot’s server-side caching means very recently published changes might take a few minutes to propagate before Getmd’s conversion picks them up.
HubDB dynamic content. If your HubSpot pages use HubDB for dynamic data tables, that content is rendered server-side and included in the HTML – Getmd captures it correctly. However, HubDB data that loads client-side (via JavaScript) may not appear in the markdown conversion.
Multi-language content. HubSpot’s multi-language feature creates separate page variants with different URLs. Each language variant is a separate page from Getmd’s perspective and gets its own markdown conversion. Your llms.txt should reference the primary language pages.
Shopify
Shopify sites come to Getmd for a different reason than WordPress or HubSpot sites. Ecommerce businesses want their products to appear when AI systems answer shopping-related questions – “best running shoes under $150,” “compare wireless earbuds,” “which CRM integrates with Shopify.” Product pages, collection pages, and blog content all matter for AI visibility.
How Getmd handles Shopify
Product pages are Shopify’s most important content type for AI readability. Getmd extracts the product title, description, pricing, variant information, and key specifications. Product images are referenced with alt text. Review content (if rendered server-side) is included.
Collection pages get converted with the collection description and product listings. These pages are useful for AI systems answering category-level questions.
Blog posts on Shopify convert cleanly – Shopify’s blog HTML is relatively standard.
The Liquid templating layer. Shopify uses Liquid templates that are rendered server-side. Getmd receives the rendered HTML, not the Liquid source, so template complexity doesn’t affect conversion quality.
Shopify-specific considerations
JavaScript-rendered content. Many Shopify themes load reviews, recommendations, and dynamic pricing through JavaScript after the initial page load. Since Getmd converts the initial HTML response, content that depends on JavaScript execution may not appear. If important product information (like review summaries or dynamic pricing) is missing from your markdown, check whether it’s loaded via JavaScript on your live site.
Product variants. Shopify product variants (sizes, colours, configurations) are typically handled through JavaScript selectors. The base product information and description will convert, but variant-specific details may not appear unless they’re part of the static HTML.
Apps and widgets. Third-party Shopify apps that inject content (reviews, size guides, shipping calculators) may or may not appear in the markdown depending on whether they render server-side or client-side.
Webflow
Webflow sites tend to produce some of the cleanest initial conversions, because Webflow generates relatively semantic HTML. But there are still platform-specific nuances worth understanding.
How Getmd handles Webflow
Standard pages – about pages, service pages, landing pages – convert well. Webflow’s HTML structure uses semantic elements and relatively clean class naming. Getmd strips the Webflow-specific classes and converts the content cleanly.
CMS collection pages (Webflow’s dynamic content system) render server-side and convert normally. Blog posts, case studies, team pages, and other collection-based content all work well.
Interactions and animations. Webflow’s interaction system (scroll-triggered animations, hover effects, parallax) doesn’t affect the content conversion – these are visual effects handled by JavaScript that don’t alter the text content.
Webflow-specific considerations
Webflow’s JavaScript bundle. Every Webflow site includes a Webflow JavaScript file that handles interactions and form submissions. Getmd strips this, but if your site uses Webflow’s JavaScript for content display (show/hide sections, tabbed content), those dynamically-shown sections may not appear in the markdown.
Rich text vs custom layouts. Content in Webflow Rich Text fields converts very cleanly. Content in custom-built layout sections (using Webflow’s visual builder) may have more structural noise, though Getmd handles the common patterns.
Hosting and CDN. Webflow hosts sites on its own CDN with SSL. Getmd fetches through this layer without issues.
Cross-platform considerations
Regardless of your CMS, a few principles apply:
Server-rendered content converts reliably. Any content that’s part of the HTML your server sends to the browser will convert to markdown. Content that loads after the page renders via JavaScript may not.
Your existing website doesn’t change. Getmd doesn’t install anything on your server, modify your CMS, or alter your pages. It fetches your HTML the same way any browser would, converts it, and serves the markdown from your Getmd subdomain.
Different page types may convert differently. Your homepage (often layout-heavy with little text) will produce sparser markdown than your blog posts (text-heavy with clear content structure). This is normal and expected – AI systems are more interested in your content pages than your visual-heavy landing pages.
Test your key pages. After connecting your site, check the markdown output for your 5–10 most important pages. If the conversion looks clean on those, you’re in good shape. If any show issues, Getmd’s support can help adjust the extraction for your specific setup.
Choosing your plan
Getmd’s pricing works the same regardless of your CMS:
Starter ($79/month) – Ideal for a single site with up to a few hundred pages. Full analytics, llms.txt hosting, and live markdown conversion included.
Growth ($129/month) – For larger sites or more active content strategies. Higher usage limits and priority cache refresh.
Agency ($199/month) – For agencies managing multiple client websites. Multi-site management and dedicated support.
All plans include the full analytics dashboard – because knowing which AI systems are reading your content matters regardless of your CMS.
Connect your website in 5 minutes – any CMS. Start your free trial →
This is part of our series on making your website visible to AI. Also in this series:
- Introducing Getmd: Make Your Website Visible to AI
- What is Markdown and Why Every AI System Prefers It
- What is llms.txt? The Discovery File AI Crawlers Actually Read
- llms.txt vs llms-full.txt: What the Data Actually Shows
- Why Getmd Converts Live and Caches Every 5 Minutes
- The Clean Markdown Problem: Why Most Converters Produce Garbage
- Which AI Bots Are Visiting Your Website? (And Which Aren’t)
- How to Read Your AI Crawler Analytics and Fix What’s Broken
- Getting Started with Getmd: Connect Your Website in 5 Minutes
