Every change to make in the website code, in one call.
The whole fix list as structured rows, so an assistant can apply them without assembling them from a dozen endpoints. Each row names the page, what it reads now, and the exact change. A row with in_page_code true is a markup or wording edit you can make in the site source; a row with it false needs a person to write new content. To raise these as a pull request instead, use POST /sites/{site_id}/code/repos/{repo_id}/fixes, then POST /code/fixes/{fix_set_id}/files; a person presses Push. Measured from the last crawl, so crawl again after shipping.
GET
https://app.softsolz.uk/api/v1/services/seo/sites/{site_id}/code-changesRecent Requests
Log in to see full request historyTimeStatusUser Agent
Make a request to see history.
Path Params
site_idstringrequiredHeaders
AuthorizationstringrequiredBearer token: `Bearer sk_live_...` (or `sk_test_...` for sandbox). A login token will not work here.
Response
Response Body
changesarray of objectsHighest severity first.countsobjectHow many are code edits and how many need writing.schema_examplestringA JSON-LD block to copy when structured data is missing.how_to_applystringWhat to do with these rows.notestringWhat this was measured from.Request
import { SoftSolz } from '@softsolz/sdk';
const client = new SoftSolz({ apiKey: process.env.SOFTSOLZ_API_KEY });
const result = await client.seo.listCodeChanges('<site_id>');console.log(result);Credentials
Sent as a Bearer token. Stored only in your browser.
Response · 200
{ "data": { "changes": [], "counts": {}, "schema_example": "string", "how_to_apply": "string", "note": "string" }}