<?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: Sullivan Rutherford Estate</title>
    <description>The latest articles on DEV Community by Sullivan Rutherford Estate (@sullivanwine).</description>
    <link>https://dev.to/sullivanwine</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3810665%2F49f0d858-0767-434c-aba6-471fad49d04e.png</url>
      <title>DEV Community: Sullivan Rutherford Estate</title>
      <link>https://dev.to/sullivanwine</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sullivanwine"/>
    <language>en</language>
    <item>
      <title>Technical SEO Lessons from Optimizing a Winery Website</title>
      <dc:creator>Sullivan Rutherford Estate</dc:creator>
      <pubDate>Fri, 06 Mar 2026 22:32:32 +0000</pubDate>
      <link>https://dev.to/sullivanwine/technical-seo-lessons-from-optimizing-a-winery-website-3gcc</link>
      <guid>https://dev.to/sullivanwine/technical-seo-lessons-from-optimizing-a-winery-website-3gcc</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwqrm1lzpxd73ccvj4otk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwqrm1lzpxd73ccvj4otk.png" alt=" " width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Many developers think SEO is mostly about keywords and content, but technical issues can quietly impact a site's visibility and performance.&lt;/p&gt;

&lt;p&gt;Recently I worked on improving the website for &lt;a href="https://sullivanwine.com/" rel="noopener noreferrer"&gt;Sullivan Rutherford Estate&lt;/a&gt;, a luxury winery in Napa Valley. During the audit we uncovered several technical issues that are surprisingly common across WordPress sites.&lt;/p&gt;

&lt;p&gt;Here are three fixes that made an immediate difference.&lt;/p&gt;

&lt;p&gt;Eliminating Redirect Chains&lt;/p&gt;

&lt;p&gt;The site had multiple redirects between HTTP, HTTPS, and canonical versions of URLs. While each redirect worked individually, the chain slowed crawling and added unnecessary server requests.&lt;/p&gt;

&lt;p&gt;Example chain:&lt;/p&gt;

&lt;p&gt;&lt;a href="http://domain.com" rel="noopener noreferrer"&gt;http://domain.com&lt;/a&gt;&lt;br&gt;
 → &lt;a href="https://domain.com" rel="noopener noreferrer"&gt;https://domain.com&lt;/a&gt;&lt;br&gt;
 → &lt;a href="https://www.domain.com" rel="noopener noreferrer"&gt;https://www.domain.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Instead, the goal is a single redirect directly to the canonical version.&lt;/p&gt;

&lt;p&gt;Updating the .htaccess rules ensured all requests went straight to the final URL. This simplified the redirect structure and improved crawl efficiency.&lt;/p&gt;

&lt;p&gt;Reducing Image Bloat&lt;/p&gt;

&lt;p&gt;Like many visually rich websites, the winery site relies heavily on photography. The problem was that many images were uploaded without optimization.&lt;/p&gt;

&lt;p&gt;Issues included:&lt;/p&gt;

&lt;p&gt;• Large file sizes (often multiple MB)&lt;br&gt;
• Images larger than their display container&lt;br&gt;
• Lack of modern compression formats&lt;/p&gt;

&lt;p&gt;By resizing images to the correct dimensions and compressing them before upload, the overall page weight dropped significantly.&lt;/p&gt;

&lt;p&gt;This is especially important for image-heavy sites where photography plays a central role in the user experience.&lt;/p&gt;

&lt;p&gt;Improving Alt Text for Accessibility&lt;/p&gt;

&lt;p&gt;Another issue we found was inconsistent or missing alt attributes on images.&lt;/p&gt;

&lt;p&gt;Alt text serves two key purposes:&lt;/p&gt;

&lt;p&gt;• Accessibility for screen readers&lt;br&gt;
• Context for search engines&lt;/p&gt;

&lt;p&gt;Instead of leaving alt attributes empty, we rewrote them to describe the visual content of the image and its context.&lt;/p&gt;

&lt;p&gt;Example:&lt;/p&gt;

&lt;p&gt;alt="Cabernet Sauvignon vines at Sullivan Rutherford Estate in Napa Valley"&lt;/p&gt;

&lt;p&gt;This small change improves accessibility and helps search engines better understand page content.&lt;/p&gt;

&lt;p&gt;Monitoring Improvements&lt;/p&gt;

&lt;p&gt;After the fixes were implemented, we re-ran technical audits and monitored the improvements in crawl reports and site health metrics.&lt;/p&gt;

&lt;p&gt;While none of these fixes were particularly complex, together they significantly improved the site’s technical foundation.&lt;/p&gt;

&lt;p&gt;Final Thoughts&lt;/p&gt;

&lt;p&gt;Technical SEO often overlaps with everyday development work. Redirect logic, media optimization, and accessibility attributes all play a role in how search engines crawl and evaluate a website.&lt;/p&gt;

&lt;p&gt;For developers maintaining WordPress sites, it is worth auditing these areas regularly.&lt;/p&gt;

&lt;p&gt;Small improvements in the technical layer can have a meaningful impact on performance, accessibility, and search visibility.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>wordpress</category>
    </item>
  </channel>
</rss>
