<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Zlatko Marjanovic</title>
    <description>The latest articles on DEV Community by Zlatko Marjanovic (@zlatko_marjanovic_a206f1e).</description>
    <link>https://dev.to/zlatko_marjanovic_a206f1e</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4114158%2Ffc743fc9-06ab-4752-b4f1-97a9dc394d66.png</url>
      <title>DEV Community: Zlatko Marjanovic</title>
      <link>https://dev.to/zlatko_marjanovic_a206f1e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zlatko_marjanovic_a206f1e"/>
    <language>en</language>
    <item>
      <title>Website Strategy Consultant: What Good Discovery Actually Covers</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:59:15 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/website-strategy-consultant-what-good-discovery-actually-covers-57dc</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/website-strategy-consultant-what-good-discovery-actually-covers-57dc</guid>
      <description>&lt;p&gt;Good website strategy discovery produces written decisions on audience, offer, architecture, proof, SEO inventory, and CMS, not a moodboard.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Discovery is a decision set: ICP, offer, IA, proof, SEO inventory, CMS model.&lt;/li&gt;
&lt;li&gt;Moodboards can wait until those artifacts exist.&lt;/li&gt;
&lt;li&gt;SEO inventory belongs in strategy, not as a post-launch apology.&lt;/li&gt;
&lt;li&gt;This role is not a fractional CTO and not a product consultant for authenticated apps.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full walkthrough: &lt;a href="https://zlatkomarjanovic.com/blog/website-strategy-consultant-what-good-discovery-actually-covers" rel="noopener noreferrer"&gt;Website Strategy Consultant: What Good Discovery Actually Covers&lt;/a&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>startup</category>
      <category>webdev</category>
      <category>design</category>
    </item>
    <item>
      <title>AI Search Optimization Guide for Service Businesses</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:50:35 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/ai-search-optimization-guide-for-service-businesses-3eid</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/ai-search-optimization-guide-for-service-businesses-3eid</guid>
      <description>&lt;p&gt;Service businesses win AI search by making services, proof, FAQs, and booking pages quoteable and crawlable, not by publishing a SaaS-scale blog.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Service businesses need four quoteable templates: services, proof, FAQs, booking.&lt;/li&gt;
&lt;li&gt;Write the offer the way you say it on a call, in HTML a crawler can fetch.&lt;/li&gt;
&lt;li&gt;Keep FAQs as visible content. Do not chase retired Google FAQ rich results.&lt;/li&gt;
&lt;li&gt;A citation that cannot start an engagement is an incomplete win.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full walkthrough: &lt;a href="https://zlatkomarjanovic.com/blog/ai-search-optimization-guide-for-service-businesses" rel="noopener noreferrer"&gt;AI Search Optimization Guide for Service Businesses&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>career</category>
      <category>startup</category>
    </item>
    <item>
      <title>Technical SEO Consultant vs SEO Agency: What Growing Companies Actually Need</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:49:58 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/technical-seo-consultant-vs-seo-agency-what-growing-companies-actually-need-3k07</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/technical-seo-consultant-vs-seo-agency-what-growing-companies-actually-need-3k07</guid>
      <description>&lt;p&gt;Hire a technical SEO consultant for migrations, indexation, and rendering issues; hire an agency when the site is healthy and you need production capacity.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Consultants fix systems. Agencies run programs.&lt;/li&gt;
&lt;li&gt;Buy content only after the templates can support it.&lt;/li&gt;
&lt;li&gt;Interview people on your live coverage report.&lt;/li&gt;
&lt;li&gt;Hybrid works: specialist first, production second.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full walkthrough: &lt;a href="https://zlatkomarjanovic.com/blog/technical-seo-consultant-vs-seo-agency-what-growing-companies-actually-need" rel="noopener noreferrer"&gt;Technical SEO Consultant vs SEO Agency: What Growing Companies Actually Need&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>career</category>
      <category>startup</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Schema Markup for SEO: What Worthwhile Sites Actually Implement</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:44:54 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/schema-markup-for-seo-what-worthwhile-sites-actually-implement-3hp0</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/schema-markup-for-seo-what-worthwhile-sites-actually-implement-3hp0</guid>
      <description>&lt;p&gt;Implement only Google-documented schema types that match visible content, and skip FAQPage rich-result tactics and fake ratings.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Only implement Google-supported types that match visible content.&lt;/li&gt;
&lt;li&gt;Article or BlogPosting, BreadcrumbList, Person, Organization, and WebSite cover most marketing sites.&lt;/li&gt;
&lt;li&gt;Do not add FAQPage to chase Google rich results after the May 2026 retirement.&lt;/li&gt;
&lt;li&gt;Never ship fake ratings or review markup you cannot show on the page.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full walkthrough: &lt;a href="https://zlatkomarjanovic.com/blog/schema-markup-for-seo-what-worthwhile-sites-actually-implement" rel="noopener noreferrer"&gt;Schema Markup for SEO: What Worthwhile Sites Actually Implement&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>llms.txt for SEO: Does It Help AI Search Visibility?</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:44:48 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/llmstxt-for-seo-does-it-help-ai-search-visibility-56kh</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/llmstxt-for-seo-does-it-help-ai-search-visibility-56kh</guid>
      <description>&lt;p&gt;llms.txt is an optional map for some AI crawlers; Google Search does not use special AI files for ranking, so do not claim a ranking benefit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Google Search does not use llms.txt or similar special AI files for ranking.&lt;/li&gt;
&lt;li&gt;Some non-Google crawlers may use the file as a courtesy map. That is optional.&lt;/li&gt;
&lt;li&gt;If you keep one, list only canonical URLs you still stand behind.&lt;/li&gt;
&lt;li&gt;robots.txt, indexable HTML, and unique pages still decide visibility.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full walkthrough: &lt;a href="https://zlatkomarjanovic.com/blog/llms-txt-for-seo-does-it-help-ai-search-visibility" rel="noopener noreferrer"&gt;llms.txt for SEO: Does It Help AI Search Visibility?&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>webdev</category>
      <category>discuss</category>
    </item>
    <item>
      <title>How to Rank in AI Overviews Without Chasing Shortcuts</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:38:41 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/how-to-rank-in-ai-overviews-without-chasing-shortcuts-3nlf</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/how-to-rank-in-ai-overviews-without-chasing-shortcuts-3nlf</guid>
      <description>&lt;p&gt;To appear in Google AI Overviews you need an indexed, snippet-eligible page with unique value and clear facts, not a schema or file-format shortcut.&lt;/p&gt;

&lt;p&gt;I wrote the long version because teams keep treating this as a slogan instead of a sequence. The short version is still useful: decide what the page or site is actually for, then protect the URLs, the offer, and the HTML Google can fetch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this actually means
&lt;/h2&gt;

&lt;p&gt;Google's current AI Overviews guidance: indexed pages, unique value, clear facts. No special schema, no llms.txt ranking trick, no FAQ markup hack.&lt;/p&gt;

&lt;p&gt;Most of the damage I see is not a missing plugin. It is a missing owner. Someone redesigned the template, dropped a title, hid the copy behind a click, or launched without a redirect map. Then they asked why traffic moved.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts I would not skip
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;AI Overviews use indexed, snippet-eligible pages. There is no extra technical membership.&lt;/li&gt;
&lt;li&gt;Google does not require special schema or AI files for these features.&lt;/li&gt;
&lt;li&gt;Unique, non-commodity pages beat thin variants for every fan-out query.&lt;/li&gt;
&lt;li&gt;Measure in Search Console, not an unverifiable mention tracker.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you only do one thing, do the inventory first. Crawl the current site. Export Search Console. Write down the URLs that already earn clicks or conversations. Those pages are the contract. Everything else is decoration until that list is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I would use this
&lt;/h2&gt;

&lt;p&gt;I treat this as a working note, not a manifesto. Use it before you hire, before you migrate, or before you open a new design file. If the current site already works, do not blow it up for a moodboard.&lt;/p&gt;

&lt;p&gt;This is an adapted version of a longer guide. The full walkthrough, examples, and implementation notes live on my site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://zlatkomarjanovic.com/blog/how-to-rank-in-ai-overviews-without-chasing-shortcuts" rel="noopener noreferrer"&gt;Read the full article: How to Rank in AI Overviews Without Chasing Shortcuts&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>google</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Generative Engine Optimization Explained Without the Hype</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:38:39 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/generative-engine-optimization-explained-without-the-hype-1m1m</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/generative-engine-optimization-explained-without-the-hype-1m1m</guid>
      <description>&lt;p&gt;GEO is a label for retrieval: unique people-first pages that can be crawled and cited, not a product, file format, or schema trick.&lt;/p&gt;

&lt;p&gt;I wrote the long version because teams keep treating this as a slogan instead of a sequence. The short version is still useful: decide what the page or site is actually for, then protect the URLs, the offer, and the HTML Google can fetch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this actually means
&lt;/h2&gt;

&lt;p&gt;Generative engine optimization is people-first content, crawlability, and citations. Google does not need special AI files or schema hacks.&lt;/p&gt;

&lt;p&gt;Most of the damage I see is not a missing plugin. It is a missing owner. Someone redesigned the template, dropped a title, hid the copy behind a click, or launched without a redirect map. Then they asked why traffic moved.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts I would not skip
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;GEO describes retrieval by generative systems. It is not a Google ranking factor you can buy.&lt;/li&gt;
&lt;li&gt;People-first, non-commodity content plus crawlability is the real work.&lt;/li&gt;
&lt;li&gt;Google says you can ignore special AI files, chunking, and extra schema for Search AI features.&lt;/li&gt;
&lt;li&gt;Keep GEO, AEO, and AI Overviews on separate URLs so they do not cannibalize.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you only do one thing, do the inventory first. Crawl the current site. Export Search Console. Write down the URLs that already earn clicks or conversations. Those pages are the contract. Everything else is decoration until that list is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I would use this
&lt;/h2&gt;

&lt;p&gt;I treat this as a working note, not a manifesto. Use it before you hire, before you migrate, or before you open a new design file. If the current site already works, do not blow it up for a moodboard.&lt;/p&gt;

&lt;p&gt;This is an adapted version of a longer guide. The full walkthrough, examples, and implementation notes live on my site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://zlatkomarjanovic.com/blog/generative-engine-optimization-explained-without-the-hype" rel="noopener noreferrer"&gt;Read the full article: Generative Engine Optimization Explained Without the Hype&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>webdev</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Answer Engine Optimization: What to Fix on Your Site First</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:33:35 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/answer-engine-optimization-what-to-fix-on-your-site-first-2clf</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/answer-engine-optimization-what-to-fix-on-your-site-first-2clf</guid>
      <description>&lt;p&gt;Start answer engine optimization with titles, extractable answers, crawlable HTML, identity, and internal links on pages you already have.&lt;/p&gt;

&lt;p&gt;I wrote the long version because teams keep treating this as a slogan instead of a sequence. The short version is still useful: decide what the page or site is actually for, then protect the URLs, the offer, and the HTML Google can fetch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this actually means
&lt;/h2&gt;

&lt;p&gt;The first 10 answer engine optimization fixes: titles, extractable answers, crawlable HTML, author identity, and internal links.&lt;/p&gt;

&lt;p&gt;Most of the damage I see is not a missing plugin. It is a missing owner. Someone redesigned the template, dropped a title, hid the copy behind a click, or launched without a redirect map. Then they asked why traffic moved.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts I would not skip
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Fix retrieval hygiene on existing pages before you add an AEO content calendar.&lt;/li&gt;
&lt;li&gt;Titles, a quoteable answer, and crawlable HTML matter more than a new acronym.&lt;/li&gt;
&lt;li&gt;Author and organization identity should match the visible site.&lt;/li&gt;
&lt;li&gt;FAQ text can stay; FAQ rich results in Google Search were retired in May 2026.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you only do one thing, do the inventory first. Crawl the current site. Export Search Console. Write down the URLs that already earn clicks or conversations. Those pages are the contract. Everything else is decoration until that list is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I would use this
&lt;/h2&gt;

&lt;p&gt;I treat this as a working note, not a manifesto. Use it before you hire, before you migrate, or before you open a new design file. If the current site already works, do not blow it up for a moodboard.&lt;/p&gt;

&lt;p&gt;This is an adapted version of a longer guide. The full walkthrough, examples, and implementation notes live on my site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://zlatkomarjanovic.com/blog/answer-engine-optimization-what-to-fix-on-your-site-first" rel="noopener noreferrer"&gt;Read the full article: Answer Engine Optimization: What to Fix on Your Site First&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>webdev</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>What a Conversion Rate Optimization Agency Should Fix Before Running Tests</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:33:30 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/what-a-conversion-rate-optimization-agency-should-fix-before-running-tests-1jgf</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/what-a-conversion-rate-optimization-agency-should-fix-before-running-tests-1jgf</guid>
      <description>&lt;p&gt;Do not run A/B tests until tracking, the offer, a single primary action, and the mobile path are honest.&lt;/p&gt;

&lt;p&gt;I wrote the long version because teams keep treating this as a slogan instead of a sequence. The short version is still useful: decide what the page or site is actually for, then protect the URLs, the offer, and the HTML Google can fetch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this actually means
&lt;/h2&gt;

&lt;p&gt;A CRO agency should fix tracking, offer, CTA competition, proof placement, and mobile completion before it sells you an A/B testing calendar.&lt;/p&gt;

&lt;p&gt;Most of the damage I see is not a missing plugin. It is a missing owner. Someone redesigned the template, dropped a title, hid the copy behind a click, or launched without a redirect map. Then they asked why traffic moved.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts I would not skip
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Broken tracking makes every test fictional.&lt;/li&gt;
&lt;li&gt;Competing CTAs are a structure problem, not a variant problem.&lt;/li&gt;
&lt;li&gt;Month one should produce a do-not-test-yet list.&lt;/li&gt;
&lt;li&gt;Guaranteed lift percentages are a warning sign.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you only do one thing, do the inventory first. Crawl the current site. Export Search Console. Write down the URLs that already earn clicks or conversations. Those pages are the contract. Everything else is decoration until that list is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I would use this
&lt;/h2&gt;

&lt;p&gt;I treat this as a working note, not a manifesto. Use it before you hire, before you migrate, or before you open a new design file. If the current site already works, do not blow it up for a moodboard.&lt;/p&gt;

&lt;p&gt;This is an adapted version of a longer guide. The full walkthrough, examples, and implementation notes live on my site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://zlatkomarjanovic.com/blog/what-a-conversion-rate-optimization-agency-should-fix-before-running-tests" rel="noopener noreferrer"&gt;Read the full article: What a Conversion Rate Optimization Agency Should Fix Before Running Tests&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>startup</category>
      <category>marketing</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Headless CMS for Marketing Teams: When Webflow or Framer Is Not Enough</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:28:28 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/headless-cms-for-marketing-teams-when-webflow-or-framer-is-not-enough-dd</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/headless-cms-for-marketing-teams-when-webflow-or-framer-is-not-enough-dd</guid>
      <description>&lt;p&gt;Choose headless plus Next.js when preview, roles, locales, and template SEO outgrow a visual CMS. Most marketing sites should stay put until that pain is real.&lt;/p&gt;

&lt;p&gt;I wrote the long version because teams keep treating this as a slogan instead of a sequence. The short version is still useful: decide what the page or site is actually for, then protect the URLs, the offer, and the HTML Google can fetch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this actually means
&lt;/h2&gt;

&lt;p&gt;When a headless CMS plus Next.js beats Webflow or Framer for marketing teams: preview, roles, localization, structured content, and SEO at scale.&lt;/p&gt;

&lt;p&gt;Most of the damage I see is not a missing plugin. It is a missing owner. Someone redesigned the template, dropped a title, hid the copy behind a click, or launched without a redirect map. Then they asked why traffic moved.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts I would not skip
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Most marketing sites do not need headless yet.&lt;/li&gt;
&lt;li&gt;Move when preview, roles, locales, or template SEO outgrow the visual CMS.&lt;/li&gt;
&lt;li&gt;Headless is an extra system to staff, not a ranking upgrade by itself.&lt;/li&gt;
&lt;li&gt;Scope the move like a product: ownership, preview, and URL preservation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you only do one thing, do the inventory first. Crawl the current site. Export Search Console. Write down the URLs that already earn clicks or conversations. Those pages are the contract. Everything else is decoration until that list is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I would use this
&lt;/h2&gt;

&lt;p&gt;I treat this as a working note, not a manifesto. Use it before you hire, before you migrate, or before you open a new design file. If the current site already works, do not blow it up for a moodboard.&lt;/p&gt;

&lt;p&gt;This is an adapted version of a longer guide. The full walkthrough, examples, and implementation notes live on my site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://zlatkomarjanovic.com/blog/headless-cms-for-marketing-teams-when-webflow-or-framer-is-not-enough" rel="noopener noreferrer"&gt;Read the full article: Headless CMS for Marketing Teams: When Webflow or Framer Is Not Enough&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>nextjs</category>
      <category>webdev</category>
      <category>cms</category>
      <category>seo</category>
    </item>
    <item>
      <title>AEO Strategy for B2B Sites: Structure, Citations, and Content Architecture</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:28:27 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/aeo-strategy-for-b2b-sites-structure-citations-and-content-architecture-10ab</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/aeo-strategy-for-b2b-sites-structure-citations-and-content-architecture-10ab</guid>
      <description>&lt;p&gt;B2B AEO is content architecture: one winning URL per question, quoteable answers, citations, and schema that matches the page.&lt;/p&gt;

&lt;p&gt;I wrote the long version because teams keep treating this as a slogan instead of a sequence. The short version is still useful: decide what the page or site is actually for, then protect the URLs, the offer, and the HTML Google can fetch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this actually means
&lt;/h2&gt;

&lt;p&gt;An AEO strategy for B2B sites: one URL per question, extractable answers, real citations, hub-and-spoke architecture, and honest schema.&lt;/p&gt;

&lt;p&gt;Most of the damage I see is not a missing plugin. It is a missing owner. Someone redesigned the template, dropped a title, hid the copy behind a click, or launched without a redirect map. Then they asked why traffic moved.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts I would not skip
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;AEO inherits technical SEO. It does not replace it.&lt;/li&gt;
&lt;li&gt;One question, one winning URL.&lt;/li&gt;
&lt;li&gt;Cite primary sources. Do not invent stats.&lt;/li&gt;
&lt;li&gt;Schema must match visible content.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you only do one thing, do the inventory first. Crawl the current site. Export Search Console. Write down the URLs that already earn clicks or conversations. Those pages are the contract. Everything else is decoration until that list is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I would use this
&lt;/h2&gt;

&lt;p&gt;I treat this as a working note, not a manifesto. Use it before you hire, before you migrate, or before you open a new design file. If the current site already works, do not blow it up for a moodboard.&lt;/p&gt;

&lt;p&gt;This is an adapted version of a longer guide. The full walkthrough, examples, and implementation notes live on my site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://zlatkomarjanovic.com/blog/aeo-strategy-for-b2b-sites-structure-citations-and-content-architecture" rel="noopener noreferrer"&gt;Read the full article: AEO Strategy for B2B Sites: Structure, Citations, and Content Architecture&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>webdev</category>
      <category>startup</category>
    </item>
    <item>
      <title>Framer SEO: How to Build Fast Sites That Still Rank</title>
      <dc:creator>Zlatko Marjanovic</dc:creator>
      <pubDate>Mon, 07 Sep 2026 20:23:24 +0000</pubDate>
      <link>https://dev.to/zlatko_marjanovic_a206f1e/framer-seo-how-to-build-fast-sites-that-still-rank-13fe</link>
      <guid>https://dev.to/zlatko_marjanovic_a206f1e/framer-seo-how-to-build-fast-sites-that-still-rank-13fe</guid>
      <description>&lt;p&gt;Framer sites rank when pre-rendered HTML carries the copy, CMS metadata is unique, slugs stay stable, and performance work targets LCP and third parties.&lt;/p&gt;

&lt;p&gt;I wrote the long version because teams keep treating this as a slogan instead of a sequence. The short version is still useful: decide what the page or site is actually for, then protect the URLs, the offer, and the HTML Google can fetch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this actually means
&lt;/h2&gt;

&lt;p&gt;Framer SEO that actually ranks: pre-rendered HTML, CMS-bound titles, stable slugs, sitemap in Search Console, and performance without burying the copy in motion.&lt;/p&gt;

&lt;p&gt;Most of the damage I see is not a missing plugin. It is a missing owner. Someone redesigned the template, dropped a title, hid the copy behind a click, or launched without a redirect map. Then they asked why traffic moved.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts I would not skip
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Framer can rank. Confirm Googlebot gets title, H1, and copy in the HTML.&lt;/li&gt;
&lt;li&gt;Bind CMS title and description variables. Do not ship the site default on every item.&lt;/li&gt;
&lt;li&gt;Submit the custom-domain sitemap. Keep staging off the production property.&lt;/li&gt;
&lt;li&gt;Fast and rankable means LCP and third parties, not deleting every animation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you only do one thing, do the inventory first. Crawl the current site. Export Search Console. Write down the URLs that already earn clicks or conversations. Those pages are the contract. Everything else is decoration until that list is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I would use this
&lt;/h2&gt;

&lt;p&gt;I treat this as a working note, not a manifesto. Use it before you hire, before you migrate, or before you open a new design file. If the current site already works, do not blow it up for a moodboard.&lt;/p&gt;

&lt;p&gt;This is an adapted version of a longer guide. The full walkthrough, examples, and implementation notes live on my site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://zlatkomarjanovic.com/blog/framer-seo-how-to-build-fast-sites-that-still-rank" rel="noopener noreferrer"&gt;Read the full article: Framer SEO: How to Build Fast Sites That Still Rank&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>design</category>
      <category>performance</category>
    </item>
  </channel>
</rss>
