SEO Setup
alisamadiii/Portfolio
Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Install Content Freshness Signals
$ npx skills add thedaviddias/Front-End-Checklist --skill freshness -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist freshness --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/freshness .claude/skills/freshness && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "freshness" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/freshness into .claude/skills/freshness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freshness", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/freshnessType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill freshness -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist freshness --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/freshness .agents/skills/freshness && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "freshness" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/freshness into .agents/skills/freshness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freshness", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill freshness -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist freshness --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/freshness .cursor/skills/freshness && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "freshness" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/freshness into .cursor/skills/freshness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freshness", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/freshness--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill freshness -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist freshness --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/freshness .gemini/skills/freshness && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "freshness" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/freshness into .gemini/skills/freshness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freshness", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist freshnessInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill freshness -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/freshness .github/skills/freshness && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "freshness" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/freshness into .github/skills/freshness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freshness", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill freshness -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist freshness --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/freshness .opencode/skills/freshness && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "freshness" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/freshness into .opencode/skills/freshness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freshness", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
freshness- GitHub stars
- 74k
- Token cost
- ~741 tokens
- SKILL.md length
- 336 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
- Works in 5 steps: Configure your web server to send… → Update Article JSON-LD to include… → Add a visible "Last updated" date to the… → …
- Auditing blog or news pages for freshness signals
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
For each article or blog page the agent checks four things: whether the HTTP `Last-Modified` header is set and recent, whether the JSON-LD carries a `dateModified` in ISO 8601 format, whether a visible Last updated date is shown, and whether all three agree. The stated rationale is Google's Query Deserves Freshness behavior for time-sensitive queries.
Fixes include sending `Last-Modified` from the web server (an Nginx `add_header` line, or Apache with `mod_headers`), adding `dateModified` to Article JSON-LD, showing the date in the article template, and hooking the CMS or static site generator so the date changes only on substantive edits, not on metadata saves or blanket deploy timestamps. A `references/rule.md` file holds fuller examples.
When your agent uses it
- Auditing blog or news pages for freshness signals
- Setting up Last-Modified headers in an Nginx or Apache config
- Making sure dateModified updates when CMS content changes
- Reviewing a build step that stamps every page with a new date
Example prompts
- “Check our blog posts for Last-Modified headers and dateModified in the JSON-LD.”
- “Add Last-Modified to our Nginx config for the articles path.”
- “Make our Astro build pass the frontmatter updatedAt value into the Article schema.”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Configure your web server to send Last-Modified headers based on the file modification time
- Update Article JSON-LD to include dateModified
- Add a visible "Last updated" date to the article template.
- Hook your CMS to update dateModified only when content is substantively changed (not on metadata-only saves).
- If using a static site generator (Next.js, Astro), pass the frontmatter updatedAt field through to the JSON-LD and elements.
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Content Freshness Signals loads about 741 tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 336 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 336 words, ~741 tokens.
Download SKILL.mdSave it as
.claude/skills/freshness/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- freshness
- description
- 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.
- metadata.category
- seo
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/freshness
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-ModifiedHTTP response header and includedateModifiedin Article JSON-LD on all content pages - Update
dateModifiedonly 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
- Configure your web server to send
Last-Modifiedheaders based on the file modification time:- Nginx:
add_header Last-Modified $date_gmt; - Apache: ensure
mod_headersis enabled; static files serve Last-Modified automatically.
- Nginx:
- Update Article JSON-LD to include
dateModified:json { "@type": "Article", "dateModified": "2024-11-20T14:30:00Z" } - Add a visible "Last updated" date to the article template.
- Hook your CMS to update
dateModifiedonly when content is substantively changed (not on metadata-only saves). - If using a static site generator (Next.js, Astro), pass the frontmatter
updatedAtfield 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.
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/freshness of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Content Freshness Signals next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Freshness Signals this skillthedaviddias/Front-End-Checklist | 74k | — | ~741 | Automated safety check: Pass | MIT | |
| SEO Setupalisamadiii/Portfolio | 180 | — | ~1.7k | Automated safety check: Pass | None | |
| Content SEOjdevalk/skills | 105 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Persian SEOTronIsHere/vibefarsiui | 212 | — | ~1.7k | Automated safety check: Warn | MIT | |
| SEOgridaco/grida | 2.7k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| SEO Geoericrisco/rsc-harness | 180 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Content SEO
jdevalk/skills
Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness…
Persian SEO
TronIsHere/vibefarsiui
Technical and on-page SEO for Persian (Farsi) websites: lang and hreflang for fa-IR, RTL-safe metadata, Persian titles and descriptions, slug and URL strategy for Persian content, ZWNJ and keyword…
SEO
gridaco/grida
SEO best practices for the Grida project across Next.js pages, blog posts, and documentation.
SEO Geo
ericrisco/rsc-harness
A skill your agent uses when one existing page needs to rank in Google AND get cited by AI answer engines — auditing a URL for on-page SEO, structured-data JSON-LD, GEO citation levers, Core Web…
Static SEO
jdevalk/skills
Audits and improves SEO for static HTML sites. An agent skill from jdevalk/skills.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Front-End Checklist npm Package Finder
thedaviddias/Front-End-Checklist
Finds two or three well-maintained npm packages for a Front-End Checklist rule, checks download and release thresholds, and adds them to the rule's frontmatter.
Related
Categories
Questions about Content Freshness Signals
What does Content Freshness Signals do?
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches. For each article or blog page the agent checks four things: whether the HTTP `Last-Modified` header is set and recent, whether the JSON-LD carries a `dateModified` in ISO 8601 format, whether a visible Last updated date is shown, and whether all three agree. The stated rationale is Google's Query Deserves Freshness behavior for time-sensitive queries.
When should I use Content Freshness Signals?
Content Freshness Signals fits situations like: auditing blog or news pages for freshness signals; setting up Last-Modified headers in an Nginx or Apache config; making sure dateModified updates when CMS content changes; reviewing a build step that stamps every page with a new date.
How do I install Content Freshness Signals in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill freshness -a claude-code`. Or copy the skill folder (skills/freshness in thedaviddias/Front-End-Checklist) into .claude/skills/freshness in your project. Claude Code loads it when a task matches its description.
How do I install Content Freshness Signals in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill freshness -a codex`. Or copy the skill folder (skills/freshness in thedaviddias/Front-End-Checklist) into .agents/skills/freshness in your project. Codex loads it when a task matches its description.
Can I use Content Freshness Signals in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill freshness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/freshness, .gemini/skills/freshness, .github/skills/freshness and .opencode/skills/freshness in your project.
What does Content Freshness Signals need to run?
SKILL.md names no scripts, command-line tools or credentials: Content Freshness Signals is instructions for the agent only.
Does Content Freshness Signals access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Content Freshness Signals safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Content Freshness Signals use?
Content Freshness Signals is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Content Freshness Signals use?
About 741 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Content Freshness Signals?
Skills that share tags, products or a category with Content Freshness Signals: SEO Setup (alisamadiii/Portfolio, 180 stars), Content SEO (jdevalk/skills, 105 stars), Persian SEO (TronIsHere/vibefarsiui, 212 stars) and SEO (gridaco/grida, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Freshness Signals?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.