Skip to main content
POST
Internal endpoint for the Cron service to update timestamps on ALL pages for a business.
This signals freshness to AI search engines like Bing, which favor recently updated content. Updates core AI site files (llms.txt, data.json, next.config.js) AND all AI articles.
This is Job 2 in the cron sequence, running BEFORE new AI articles are created. It ensures existing content appears fresh to crawlers.

What Gets Updated

Core AI Site Files

AI Articles

For every existing AI article:

Request Body

string
required
Business identifier (org_slug)

Response

string
β€œsuccess” or β€œerror”
number
Number of core AI site files updated (llms.txt, data.json, next.config.js)
number
Number of AI articles successfully updated
number
Number of AI articles that failed to update
array
Array of updated files to deploy. Each file has path and content.
string
Vercel project name for deployment
string
AI site URL (e.g. β€œhttps://nike.searchcompany.dev”)
array
List of URL paths that were updated

Workflow

This endpoint returns files but does NOT deploy. The cron service handles deployment:

Why This Matters

From Bing’s AI Search documentation:
β€œBing’s crawl frequency and its AI tend to favor fresh content. Update your content regularly – even minor tweaks with a β€˜Last updated’ note can signal freshness. Bing might include a date in the citation (e.g., β€˜source: yoursite.com (Dec 2025)’), which can influence user trust.”
By updating timestamps daily, your pages:
  • Appear fresh to AI crawlers
  • Get higher priority in crawl scheduling
  • Show recent dates in AI citations
  • Compete better against newer content