Edit llms.txt report content
Changed onReplaces the llms.txt and llms-full.txt files of a completed llms_txt report in place, without generating them again. edits maps llms_txt and/or llms_full_txt to the full replacement text. content_version must equal result_data.content_version of the report as last read; when the report changed since, the edit is refused as stale and the message names the current version. A missing or stale content_version, a blank file, a file over 200,000 characters, a value that is not text, an unknown file key, an empty edits object, a report that has not completed or a report_type other than llms_txt is rejected with ERR_INVALID_PARAM and nothing is written. Files are stored with Unix line endings and one trailing newline. A file identical to the stored one is ignored, and the response lists the files that actually changed. The first edit keeps the generated files in original_llms_txt_content and original_llms_full_txt_content so POST /technical_geo_reports/{id}/revert_content can restore them; running the report again creates a new report without these edits. Requires a read_write scope API key and, for team members, create permission on GEO Audits.
Request
- Base URLhttps://api.llmpulse.ai/api/v1
- URLhttps://api.llmpulse.ai/api/v1/technical_geo_reports/{id}/content
- AuthAPI key in header Authorization
Path parameters
Report id returned by POST /technical_geo_reports or GET /technical_geo_reports
Request body
Example request
{
"content_version": "1790683200123456",
"edits": {
"llms_txt": "# example.com\n\n> What example.com does, in one paragraph.\n"
}
}Response
The report with its current files, plus the files that changed
Changes
- info
endpoint added
- info