Content includes freshness signals

Visitors use freshness signals as proxies for whether the product is actively maintained and whether the company is still operating. A footer copyright year that reads "© 2022" in 2026 is a four-year-old stale signal that the site has not been touched. For any product that is software — where bugs get fixed, features get added, and security matters — an outdated copyright year creates doubt about whether the company is still around. This is especially problematic for AI-built projects where the site may have been generated and deployed once, then not updated. The fix is one line of code. Blog post dates that are 18+ months old similarly signal abandonment to visitors who value recency of information.

Make the copyright year dynamic so it updates automatically each year without a code change:

// components/Footer.tsx — dynamic copyright year
export function Footer() {
  return (
    <footer>
      <p>© {new Date().getFullYear()} YourCompany. All rights reserved.</p>
    </footer>
  )
}

Find the current static copyright year in your footer component (search for the 4-digit year in components/Footer.tsx or app/layout.tsx) and replace the hardcoded year with {new Date().getFullYear()}.

For blog freshness: if the most recent post is more than 12 months old and you have no content planned, consider removing the blog listing from the main navigation rather than leaving a visibly stale blog as a trust signal. A blog that looks abandoned is worse than no blog. If content is planned, even one new post per quarter is enough to maintain freshness signals.