Author

B. Talvinder

AI Surface Maintenance Guide

Rules for keeping llms.txt, structured data, and Perplexity submission readiness current.


When to Update llms.txt

Update llms.txt whenever:

  1. New framework post published — Add to “Named Frameworks” with URL and one-line description
  2. New build-log or field-note published — Add to “Recent Build Logs” or “Recent Field Notes” (keep last 5 per section)
  3. Framework renamed or retired — Update or remove the entry
  4. New content category added — Add to “Content Categories” section
  5. New key topic emerges — Add to “Key Topics” if 2+ posts cover it
  6. Author bio changes — Update “About the Author” section

Format for new entries

- [Display Title](https://talvinder.com/{category}/{slug}/): One-line description of the core argument or concept.

Schema Checklist

The site uses JSON-LD structured data via _includes/json-ld-schema.html. Verify these are working:

Schema Type When Applied How to Verify
Person Every page (static) Check any page source for @type: Person
Article Article pages (via OG meta) Check post source for @type: Article
FAQPage Posts with .schema-faq script tag Add FAQ JSON in post frontmatter area
DefinedTerm Posts with .schema-defined-term element Add definition markup in post
BreadcrumbList Listing pages Check category index pages

When publishing a new framework:


Perplexity Submission Readiness Checklist

Before submitting to Perplexity Publishers or any AI content program:

Content readiness

Technical readiness

Identity readiness


Recurring Cadence

Task Frequency Trigger
Update llms.txt Every publish New post goes live
Verify schema Monthly check_cadence reminder
Check llms.txt accessibility Monthly Curl test
Review Perplexity readiness Quarterly Gate check