<?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: Sami</title>
    <description>The latest articles on DEV Community by Sami (@samismith).</description>
    <link>https://dev.to/samismith</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%2F4185596%2Ffbb4be75-6aab-41f4-8c51-ac1cadf3bb81.png</url>
      <title>DEV Community: Sami</title>
      <link>https://dev.to/samismith</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/samismith"/>
    <language>en</language>
    <item>
      <title>A Dental Clinic Got +247% Calls in 90 Days. The Technical Layer Did Most of the Work</title>
      <dc:creator>Sami</dc:creator>
      <pubDate>Sat, 07 Nov 2026 20:01:29 +0000</pubDate>
      <link>https://dev.to/samismith/a-dental-clinic-got-247-calls-in-90-days-the-technical-layer-did-most-of-the-work-2e18</link>
      <guid>https://dev.to/samismith/a-dental-clinic-got-247-calls-in-90-days-the-technical-layer-did-most-of-the-work-2e18</guid>
      <description>&lt;p&gt;A dental clinic went from position #6 in the Map Pack to the top 3, and total calls grew 247% — 642 tracked calls in 90 days. High-intent calls went from 25 to 61 a month.&lt;/p&gt;

&lt;p&gt;The work behind it was SEO plus email marketing. But a large part of the SEO half was technical, and it is the part developers control directly. Here is what mattered, in the order I would check it on any local-business site.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. LocalBusiness schema that matches reality
&lt;/h2&gt;

&lt;p&gt;The clinic's pages had no structured data tying the business to its services and location. Adding &lt;code&gt;LocalBusiness&lt;/code&gt; JSON-LD with the real name, address, phone, opening hours, and service list gives Google a clean entity to attach rankings and Map Pack placement to. Then validate it with &lt;a href="https://search.google.com/test/rich-results" rel="noopener noreferrer"&gt;Google's Rich Results Test&lt;/a&gt; — invalid schema is worse than no schema, because it tells Google the markup cannot be trusted.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Click-to-call that actually works on mobile
&lt;/h2&gt;

&lt;p&gt;Most of these calls come from phones. The phone number has to be a real &lt;code&gt;tel:&lt;/code&gt; link, visible without scrolling, on every service page — not an image, not a form, not a number buried in the footer. Every extra tap between "I need a dentist" and the call is a lost patient. Test it on a real phone, not just in dev tools.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Speed on the pages that convert
&lt;/h2&gt;

&lt;p&gt;Run &lt;a href="https://pagespeed.web.dev/" rel="noopener noreferrer"&gt;PageSpeed Insights&lt;/a&gt; on the service pages, not just the homepage. A homepage that scores 90 while the "dental implant cost" page loads in six seconds on mobile is a fail — the slow page is the one the high-intent searcher lands on. Watch LCP and INP on those pages specifically.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. One page per intent, one H1 per page
&lt;/h2&gt;

&lt;p&gt;The queries that converted were specific: "toothache treatment", "dental implant cost". Each one needs its own page with one H1 that matches the query, not a generic services page trying to rank for everything. That is a content decision, but it is also a routing and template decision — the site structure has to support it.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Reviews need a page to land on
&lt;/h2&gt;

&lt;p&gt;Map Pack placement leans on review signals, but a review only helps if the business it points to has a fast, working page behind it. The technical job is making sure the Google Business Profile, the site, and the schema all agree on the same name, address, and phone — and that nothing on the site 404s when a searcher clicks through.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the code did not do
&lt;/h2&gt;

&lt;p&gt;The email half — recall reminders and post-treatment follow-ups — reactivated dormant patients and drove recurring appointments. No amount of schema does that. The honest split is: the technical layer made the clinic findable and callable, and the follow-up system turned one-time searchers into returning patients.&lt;/p&gt;

&lt;p&gt;The full breakdown, with the before-and-after numbers, is in the case study: &lt;a href="https://amaranthmarketing.com/casestudies/dental-seo-case-study/" rel="noopener noreferrer"&gt;Dental SEO Case Study: +247% Calls in 90 Days&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>localbusiness</category>
      <category>technicalseo</category>
    </item>
    <item>
      <title>Technical SEO Checklist for Developers: 9 Things I Check on Every Client Site</title>
      <dc:creator>Sami</dc:creator>
      <pubDate>Wed, 14 Oct 2026 22:42:51 +0000</pubDate>
      <link>https://dev.to/samismith/technical-seo-checklist-for-developers-9-things-i-check-on-every-client-site-51bb</link>
      <guid>https://dev.to/samismith/technical-seo-checklist-for-developers-9-things-i-check-on-every-client-site-51bb</guid>
      <description>&lt;p&gt;Most sites I audit look fine in the browser and fail silently in the crawler. Here's the checklist I run on every client site before touching a single line of content. Each item is a pass/fail you can verify in minutes.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Page speed on a real mobile connection
&lt;/h2&gt;

&lt;p&gt;Run &lt;a href="https://pagespeed.web.dev/" rel="noopener noreferrer"&gt;PageSpeed Insights&lt;/a&gt; on the homepage and the two most important conversion pages. Watch LCP, INP, and CLS — Google's Core Web Vitals — not just the aggregate score. A 90+ desktop score with a 45 on mobile is a fail.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. HTTPS with no mixed content
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;curl -I https://example.com&lt;/code&gt; should return a 200 with HSTS headers. Then check for mixed-content warnings: one insecure script tag silently kills the trust signal the whole page is trying to build.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. robots.txt isn't accidentally blocking everything
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl https://example.com/robots.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I've seen &lt;code&gt;Disallow: /&lt;/code&gt; left over from staging on live sites. It takes ten seconds to check and weeks of lost indexing to discover otherwise.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Indexation coverage in Search Console
&lt;/h2&gt;

&lt;p&gt;Open Google Search Console → Pages. Sort by "Not indexed." Pages that should be indexed but aren't are a structural problem, not a content problem — crawl budget, orphan pages, or duplicate signals.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. XML sitemap exists and is submitted
&lt;/h2&gt;

&lt;p&gt;A sitemap doesn't guarantee indexing, but a missing or stale one tells Google you don't maintain the site. Generate it, submit it in Search Console, and make sure it only contains URLs you actually want indexed (no 404s, no noindex pages).&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Canonical tags on paginated and filtered pages
&lt;/h2&gt;

&lt;p&gt;Every faceted/filtered URL and every paginated archive needs a canonical tag pointing at the right version. Without them, crawl budget bleeds into duplicate variants of the same page.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Structured data validates
&lt;/h2&gt;

&lt;p&gt;Add schema.org markup for what the page actually is (Organization, LocalBusiness, FAQPage, Article) and test it with &lt;a href="https://search.google.com/test/rich-results" rel="noopener noreferrer"&gt;Google's Rich Results Test&lt;/a&gt;. Invalid schema is worse than no schema — it tells Google the markup can't be trusted.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Plugin and script audit
&lt;/h2&gt;

&lt;p&gt;On WordPress sites: list every installed plugin and ask what each one does. The typical client site has 20+ plugins and uses 8. Each unused plugin is dead weight on every page load — and a security surface. Same rule for third-party scripts: if the analytics tag, chat widget, or font loader isn't pulling its weight, cut it.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. One H1 per page, semantic HTML
&lt;/h2&gt;

&lt;p&gt;Crawl any page and check the heading structure. Multiple H1s and div-soup layouts are still everywhere. It's a small thing, but it tells Google what the page is about — and it's free to fix.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why this order
&lt;/h2&gt;

&lt;p&gt;None of these items are content. That's the point. Content earns attention; the technical layer decides whether that content ever gets seen. If your site loads slowly, isn't crawled properly, or has a broken structure, it won't rank — no matter how good the writing is.&lt;/p&gt;

&lt;p&gt;The full non-developer explanation of this layer — what it is, why traffic-without-leads is usually a technical problem — is here: &lt;a href="https://amaranthmarketing.com/what-is-technical-seo/" rel="noopener noreferrer"&gt;Technical SEO Explained: Why Your Site Isn't Getting Leads&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Further reading: Google's &lt;a href="https://web.dev/vitals/" rel="noopener noreferrer"&gt;Web Vitals documentation&lt;/a&gt;, and &lt;a href="https://portent.com/blog/analytics/research-site-speed-hurting-everyones-revenue.htm" rel="noopener noreferrer"&gt;Portent's site-speed research&lt;/a&gt; on how load time affects conversion rates.&lt;/em&gt;&lt;/p&gt;

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