메뉴
Use when auditing article or blog pages for date markup, generating Article JSON-LD with datePublished/dateModified, or checking whether a CMS template surfaces dates correctly.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/thedaviddias/Front-End-Checklist --skill content-dates명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Use when reviewing templates, rendered HTML, or shared components related to Implement accessible breadcrumb navigation. Validate the final browser-facing markup, not just the source framework abstraction.
Use when auditing metadata, crawlability, structured data, or indexability related to Implement valid BreadcrumbList schema. Verify the rendered HTML and HTTP response rather than relying only on source files.
Use when reviewing templates, rendered HTML, or shared components related to Declare UTF-8 character encoding. Validate the final browser-facing markup, not just the source framework abstraction.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | content-dates |
| description | Use when auditing article or blog pages for date markup, generating Article JSON-LD with datePublished/dateModified, or checking whether a CMS template surfaces dates correctly. |
| metadata | {"category":"seo","priority":"medium","difficulty":"intermediate","estimatedTime":"10","source":"frontendchecklist.io","url":"https://frontendchecklist.io/en/rules/seo/content-dates"} |
Google uses publication and modification dates to assess content freshness, which influences rankings for time-sensitive queries. Visible dates also build user trust by signalling that content is current and maintained.
dateModified in JSON-LD for every article or blog post2024-03-15T10:00:00Z) in structured data; human-readable in the visible UIdateModified only when content meaningfully changes — not on trivial editsOn each article or blog page, check: (1) Is there a visible published date in the page body or byline? (2) Does the JSON-LD Article or BlogPosting block include datePublished and dateModified properties in ISO 8601 format? (3) Does the <head> include <meta property="article:published_time"> and <meta property="article:modified_time"> Open Graph tags?
<time datetime="2024-03-15">March 15, 2024</time>.datePublished and dateModified to the Article JSON-LD block:
{
"@type": "Article",
"datePublished": "2024-03-15T10:00:00Z",
"dateModified": "2024-11-20T14:30:00Z"
}
<head>:
<meta property="article:published_time" content="2024-03-15T10:00:00Z">
<meta property="article:modified_time" content="2024-11-20T14:30:00Z">
dateModified automatically on content saves.Google's freshness algorithm rewards recently published or updated content for time-sensitive queries. Structured date markup lets Google confidently surface the correct date in search snippets; without it, Google must guess from page text or HTTP headers, often producing wrong or missing dates.
Verify that Article or BlogPosting JSON-LD includes both datePublished and dateModified in ISO 8601 format. Check that <time datetime='...'> elements in the body use machine-readable dates. Confirm dateModified updates when content changes, not just on every deploy.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/seo/content-dates