본문으로 건너뛰기
cccskills
무료GitHub에 공개

freshness

Audit article update dates across the visible page, HTTP response headers, and structured data that describes the article to search engines. Align these signals with substantive content changes and review how the CMS or build process updates them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Use when auditing content pages for freshness signals, setting up HTTP Last-Modified headers in a web server config, or ensuring Article JSON-LD dateModified is updated when CMS content changes.

설치 방법 보기

이럴 때 유용합니다

  • Auditing update dates on articles and blog posts
  • Reviewing CMS rules for updating modification dates
  • Checking timestamps applied during static site deployments

포함된 파일(2)

  • SKILL.md2.9 KB
  • references/rule.md4.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Show content freshness signals

Google's Query Deserves Freshness (QDF) algorithm boosts recent or recently updated content for time-sensitive queries. Missing or stale freshness signals mean your updated content competes without the freshness advantage it deserves.

Quick Reference

  • Set the Last-Modified HTTP response header and include dateModified in Article JSON-LD on all content pages
  • Update dateModified only when content substantively changes — trivial edits should not alter the date
  • For time-sensitive topics (news, tutorials, product reviews), freshness directly influences Google's ranking of your content

Check

For each article or blog page: (1) Check the HTTP response Last-Modified header — is it set and recent? (2) Check the JSON-LD for a dateModified property in ISO 8601 format. (3) Is a visible 'Last updated' date shown to users? (4) Is the dateModified in JSON-LD consistent with the visible date and the Last-Modified header?

Fix

  1. Configure your web server to send Last-Modified headers based on the file modification time:
    • Nginx: add_header Last-Modified $date_gmt;
    • Apache: ensure mod_headers is enabled; static files serve Last-Modified automatically.
  2. Update Article JSON-LD to include dateModified:
    { "@type": "Article", "dateModified": "2024-11-20T14:30:00Z" }
    
  3. Add a visible "Last updated" date to the article template.
  4. Hook your CMS to update dateModified only when content is substantively changed (not on metadata-only saves).
  5. If using a static site generator (Next.js, Astro), pass the frontmatter updatedAt field through to the JSON-LD and <time> elements.

Explain

Google's freshness algorithm (QDF — Query Deserves Freshness) actively boosts recently published or updated content for searches where recency matters. If your dateModified is stale or absent, Google may not credit your content with the freshness it deserves, ranking older competitors above you even after you have updated the article.

Code Review

Check that the Last-Modified response header is present on article pages. Verify Article JSON-LD includes dateModified in ISO 8601 format. Confirm that the build or deployment system updates dateModified only for content files that actually changed — not a blanket timestamp update on all pages during deploy.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/seo/freshness

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

404-page

무료

Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating a helpful custom 404 page
  • Adding search and navigation for broken links
  • Checking missing pages that return HTTP 200
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing a website’s About page
  • Creating a page about the organization and its mission
  • Checking how operator information appears in rendered output
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Review accessibility coverage for shared components
  • Add accessibility checks to page flow tests
  • Run accessibility tests in CI
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing accessibility across the sign-in process
  • Checking verification code paste and autofill
  • Inspecting password reset and account recovery
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing form error announcements
  • Checking success message display duration
  • Auditing live update notifications
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing tables for screen reader accessibility
  • Checking header relationships in tables with merged cells
  • Reviewing table patterns in a design system
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

thedaviddias의 스킬 모두 보기

이 스킬의 문제 신고