<?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: Emmanuel Oluwaseun</title>
    <description>The latest articles on DEV Community by Emmanuel Oluwaseun (@emmanuel_oluwaseun_e1eff9).</description>
    <link>https://dev.to/emmanuel_oluwaseun_e1eff9</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%2F4231256%2Fb48eb4b0-df0e-4b88-965b-1a3ea850ce0d.png</url>
      <title>DEV Community: Emmanuel Oluwaseun</title>
      <link>https://dev.to/emmanuel_oluwaseun_e1eff9</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/emmanuel_oluwaseun_e1eff9"/>
    <language>en</language>
    <item>
      <title>What your homepage looks like to Google and AI crawlers: a 20-minute checklist</title>
      <dc:creator>Emmanuel Oluwaseun</dc:creator>
      <pubDate>Sat, 07 Nov 2026 01:13:02 +0000</pubDate>
      <link>https://dev.to/emmanuel_oluwaseun_e1eff9/what-your-homepage-looks-like-to-google-and-ai-crawlers-a-20-minute-checklist-emk</link>
      <guid>https://dev.to/emmanuel_oluwaseun_e1eff9/what-your-homepage-looks-like-to-google-and-ai-crawlers-a-20-minute-checklist-emk</guid>
      <description>&lt;p&gt;Your site can look great in a browser and still be half-invisible to search engines and AI assistants, because they read the code, not the pixels. Here's a quick pass you can do on any homepage.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The basics in &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt;
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;One unique &lt;code&gt;&amp;lt;title&amp;gt;&lt;/code&gt; (~50–60 chars) that says what you do and where.&lt;/li&gt;
&lt;li&gt;A &lt;code&gt;&amp;lt;meta name="description"&amp;gt;&lt;/code&gt; written for humans, since it's often your search snippet.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;&amp;lt;meta name="viewport" content="width=device-width, initial-scale=1"&amp;gt;&lt;/code&gt;. Without it, mobile rendering suffers.&lt;/li&gt;
&lt;li&gt;Open Graph tags (&lt;code&gt;og:title&lt;/code&gt;, &lt;code&gt;og:description&lt;/code&gt;, &lt;code&gt;og:image&lt;/code&gt;) so shared links get a proper preview.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. Structure
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Exactly one &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt;, then headings in order. Crawlers use them to work out what the page is about.&lt;/li&gt;
&lt;li&gt;Meaningful &lt;code&gt;alt&lt;/code&gt; text on images that carry information.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  3. Discoverability
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;/robots.txt&lt;/code&gt; exists and doesn't accidentally block everything.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;/sitemap.xml&lt;/code&gt; exists and is referenced in robots.txt.&lt;/li&gt;
&lt;li&gt;Structured data (JSON-LD), e.g. &lt;code&gt;LocalBusiness&lt;/code&gt; or &lt;code&gt;Organization&lt;/code&gt; with name, address, phone and hours.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Quick check from the terminal:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-s&lt;/span&gt; https://yoursite.com | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-iE&lt;/span&gt; &lt;span class="s2"&gt;"&amp;lt;title&amp;gt;|name=&lt;/span&gt;&lt;span class="se"&gt;\"&lt;/span&gt;&lt;span class="s2"&gt;description&lt;/span&gt;&lt;span class="se"&gt;\"&lt;/span&gt;&lt;span class="s2"&gt;|application/ld&lt;/span&gt;&lt;span class="se"&gt;\+&lt;/span&gt;&lt;span class="s2"&gt;json|&amp;lt;h1"&lt;/span&gt;
curl &lt;span class="nt"&gt;-sI&lt;/span&gt; https://yoursite.com/sitemap.xml | &lt;span class="nb"&gt;head&lt;/span&gt; &lt;span class="nt"&gt;-1&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. Speed on a phone
&lt;/h2&gt;

&lt;p&gt;Run Lighthouse in Chrome DevTools in mobile mode. Google's "good" Core Web Vitals thresholds are LCP under 2.5s, INP under 200ms and CLS under 0.1. The usual culprits are oversized hero images, render-blocking scripts and web fonts.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Can someone actually contact you?
&lt;/h2&gt;

&lt;p&gt;This is the one devs skip. Phone numbers should be &lt;code&gt;tel:&lt;/code&gt; links, emails &lt;code&gt;mailto:&lt;/code&gt;, WhatsApp a &lt;code&gt;https://wa.me/&lt;/code&gt; link, and a contact or booking action should be visible without scrolling on mobile. If it's only an image or plain text, a lot of visitors (and tools) won't act on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Trust
&lt;/h2&gt;

&lt;p&gt;HTTPS everywhere with no mixed content, real business details, and a privacy page.&lt;/p&gt;




&lt;p&gt;That's most of what moves the needle for a small-business site. If you only do two things, fix the contact links and the mobile speed. Those tend to have the most direct effect on enquiries.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I'm with EmmaForYou. If you'd rather not do this by hand, our free website audit runs about 25 of these checks on a homepage and lists the top five fixes, with no sign-up needed: &lt;a href="https://emmaforyou.lovable.app/website-audit" rel="noopener noreferrer"&gt;https://emmaforyou.lovable.app/website-audit&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>seo</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
