Editorial standards
How SERP researches and updates these guides
SERP publishes and maintains this site. We identify the organization as the author because no individual byline has been assigned; we do not invent a writer or reviewer identity.
How product claims are checked
- Treat the implemented extension and its deterministic test evidence as the product source of truth.
- Verify provider behavior with synthetic fixtures that contain no customer, community, or private lesson data.
- Reconcile landing-page and Store claims with that evidence before launch.
- State unsupported and information-only outcomes explicitly instead of implying universal compatibility.
How external sources are selected
For browser, operating-system, provider, file-format, and command-line claims, we prefer the official documentation maintained by the relevant platform or project. Practical first-party workflows are labeled as SERP guidance and are not dressed up as independent research.
- Link to the primary documentation near the claim it supports.
- Use permission-first examples and avoid access-bypass instructions.
- Update an article when a product behavior, supported provider, or official workflow materially changes.
- Keep publication and substantive-review dates visible on article pages.
Corrections and disclosure
Send factual corrections to support@serp.store with the page URL, disputed statement, and an authoritative source when possible. SERP may sell the product discussed on this site; the commercial relationship is disclosed through the product CTAs and does not change the requirement that claims match verified behavior.