Technical SEO defaults baked into every page
When Marcus generates a page, it writes semantic HTML5 with proper heading hierarchy, alt attributes on images, and descriptive link text. Every page includes a unique meta description pulled from your content brief or auto-generated from the first paragraph. Title tags follow best-practice length and include your brand name when appropriate.
Open Graph and Twitter Card meta tags are added automatically so links shared on social platforms display rich previews with the correct image, title, and description. You don't configure these manually — Marcus infers sensible defaults from each page's content and applies them consistently across your site.
Schema.org structured data
Marcus embeds JSON-LD structured data on relevant page types. Organization schema appears on your homepage with logo, contact details, and social profiles. Article schema is added to blog posts and guides with publish date, author, and headline. FAQ schema wraps question-and-answer content when detected. This helps search engines understand your content and may enable rich results in search listings.
The structured data is generated from the content you provide in the brief or editor. Marcus does not invent review ratings, event dates, or product prices — if you need those, include the details in your content and Marcus will structure them correctly.
Sitemap.xml and robots.txt
Every Marcus project automatically generates a sitemap.xml file listing all public pages with their last-modified dates and priority hints. The sitemap updates whenever you publish or edit a page. A robots.txt file is also generated, allowing all well-behaved crawlers by default and pointing to the sitemap location.
If you need to exclude specific pages from indexing, you can set noindex directives in the page settings. Staging environments and unpublished drafts are automatically excluded from the sitemap and marked noindex to prevent premature indexing.
Mobile-first responsive design and Core Web Vitals
Marcus generates responsive CSS that adapts to any screen size, prioritizing mobile viewports first. Images are served with srcset attributes for appropriate resolution on retina and standard displays. The HTML structure and CSS load order are optimized to minimize layout shift and ensure text is visible during webfont loading.
Core Web Vitals targets are part of the default template: cumulative layout shift is minimized by reserving space for images and embeds, first contentful paint is prioritized by inlining critical CSS, and interaction-to-next-paint is kept low with minimal JavaScript. Marcus does not inject heavy analytics scripts or third-party widgets unless you explicitly add them, so the baseline performance budget is lean.
Content quality drives ranking, not templates
Marcus provides the technical foundation, but search rankings depend on factors it cannot control: the usefulness of your content, keyword relevance, topic authority, and backlinks from other sites. A well-structured page with thin or duplicate content will not rank well, no matter how clean the HTML.
Write for humans first. Answer real questions, use clear language, and provide detail where it matters. Marcus will structure that content properly, but it won't turn generic copy into high-ranking pages. If you need keyword research, competitor analysis, or link-building strategy, you'll need an SEO consultant or do that work yourself. Marcus is a builder, not a strategist.
What Marcus does not do
Marcus does not generate infinite variations of keyword-stuffed pages, create automated link schemes, or guarantee first-page rankings. It does not perform ongoing SEO audits, track rank changes, or suggest content gaps. It does not rewrite your copy to match search intent if the brief is vague or off-target.
If you need server-side rendering for JavaScript-heavy content, advanced redirect management, or multi-region hreflang tags, those features are not part of the default Builder or Studio plans. Marcus is optimized for straightforward content sites and apps where static HTML and modern CSS cover the majority of use cases.
Exporting and SEO-friendly hosting
Marcus projects are hosted on EU-based infrastructure with HTTPS enabled by default and clean, readable URLs with no session parameters or tracking tokens. If you export your project as a ZIP, you get static HTML files ready to deploy to any host. The exported sitemap, robots.txt, and meta tags remain intact, so SEO properties transfer with the code.
Custom domains on the Studio plan (€290/month for up to 25 projects) support your own domain name, which is better for brand consistency and link equity than a subdomain. The free tier and Builder plan (€29/project/month) still generate all the same SEO elements — the domain is the only difference.