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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
Last-Modified HTTP response header and include dateModified in Article JSON-LD on all content pagesdateModified only when content substantively changes — trivial edits should not alter the dateFor 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?
Last-Modified headers based on the file modification time:
add_header Last-Modified $date_gmt;mod_headers is enabled; static files serve Last-Modified automatically.dateModified:
{ "@type": "Article", "dateModified": "2024-11-20T14:30:00Z" }
dateModified only when content is substantively changed (not on metadata-only saves).updatedAt field through to the JSON-LD and <time> elements.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.
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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when reviewing templates, rendered HTML, or shared components related to Create a custom 404 error page. Validate the final browser-facing markup, not just the source framework abstraction.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing metadata, crawlability, structured data, or indexability related to Create a dedicated About page. Verify the rendered HTML and HTTP response rather than relying only on source files.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic table markup for screen readers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
日本語の概要は準備中です。原文の説明を表示しています。