This article may contain affiliate links. This is documentation-based research, not a live API test. I did not run a Surfer trial for this guide. Instead, I read the official Surfer help center pages and built an editorial review process around what the vendor documents. Where the contract is unclear, I mark it as a limitation rather than filling the gap with guesses.

Introduction

You just created a Content Editor query, and Surfer enabled Brand Knowledge by default. The profile was auto-generated from your workspace details. Now you need to decide whether to trust it for a draft that will carry your brand voice, product names, and competitive positioning. The reader task is specific: review and correct the generated profile before it shapes AI-assisted drafts, and know what to do when the profile conflicts with the brief.

The vendor documents that Brand Knowledge helps Surfer’s AI features understand your brand identity, goals, and audience, and that it is enabled by default for new Content Editor queries. It also documents that you can disable it at the fourth step of query creation, and that all AI tools use the current version of your Brand Knowledge, so replacing the profile affects even older Editors (https://docs.surferseo.com/en/articles/12631203-brand-knowledge). That last point is the reason this review matters: a profile edit is not scoped to one article.

For related background on how Surfer fits into an editorial stack, see /surfer-seo-review/. The rest of this guide is our suggested process, clearly separated from the vendor API contract.

Documented Workflow

Surfer’s documentation describes a setup path. You are prompted to add Brand Knowledge after creating a new workspace, or you can go to Settings > Workspace > Brand Knowledge. Surfer automatically generates a business description, industry or service type, topics and target audience, and competitors. You can edit, remove, or add sections and save. The vendor documents one Brand Knowledge per workspace, with no limit on regenerations, though you must wait about two minutes before generating a new version (https://docs.surferseo.com/en/articles/12631203-brand-knowledge).

Where it applies: Brand Knowledge is enabled by default when creating a new Content Editor query. You can disable it at the fourth step of query creation. It also enhances Surfy Assistant, Auto-Optimize, and Insert Outline. Existing queries created without Brand Knowledge cannot enable it later; you must create a new Content Editor document (https://docs.surferseo.com/en/articles/12631203-brand-knowledge).

The Content Editor documentation adds context: step six of the wizard lets you review competitors, toggle Brand Knowledge on or off, and add context and instructions, including source URLs. It also notes that custom instructions can be reused per user across the organization, and that Auto-Optimize suggestions can be approved or discarded (https://docs.surferseo.com/en/articles/5700347-content-editor-overview).

Our suggested process is a three-pass review before you rely on the profile. Pass one, identity: open the generated business description, industry, and audience fields and compare them to how you want to be described, not just how the site currently reads. Pass two, boundaries: inspect the competitor list and add explicit writing instructions for anything the AI should avoid, such as naming a rival or repeating a retired product term. Pass three, exceptions: note where the profile is wrong but you cannot fix it yet, and record that gap in the brief so a human catches it later. This is our editorial heuristic, not a vendor-documented workflow.

When the profile conflicts with the brief, the brief wins for that article. Do not silently edit Brand Knowledge mid-project, because the current version applies to every editor, including older ones. Example: if the profile lists a legacy product name that the brief has retired, disable Brand Knowledge for that specific query rather than rewriting the profile for one article. Exception: if the profile is missing a section you expected, verify it was generated before assuming the AI ignored it.

Editorial Decision Checklist

Use this as a pre-draft gate. It is our suggested operational checklist, not a vendor API contract.

Confirm the generated business description matches your current positioning, not a legacy tagline that still lives on an old landing page.
Check the industry or service type against the categories you actually sell into; correct it if the auto-generation picked a broader or adjacent category.
Verify the topics and target audience reflect the readers you want, not the readers you historically attracted.
Inspect the competitor list. Remove any company you do not consider a rival, and add writing instructions to avoid naming competitors if that is your policy.
Add explicit instructions for retired product terms, internal jargon, or claims the AI should not repeat.
Decide whether to disable Brand Knowledge for this query at the fourth step of query creation if the profile is materially wrong for this article.
If you disable it, record why in the brief so the next editor does not re-enable it by habit.
If you edit the profile, note the date and the reason, because the current version applies to older Editors too.
If a section is missing, verify it was generated before assuming the AI ignored it.
After the draft, review Auto-Optimize suggestions and discard any that conflict with the brief, since the vendor documents that suggestions can be approved or discarded.

A worked example: a B2B software team has a profile that lists a legacy product name. The brief for a new article uses the new name. The editor disables Brand Knowledge for that query, writes the draft with the brief’s terminology, and leaves a note in the brief. They do not rewrite Brand Knowledge for one article, because that would change the profile for every editor.

Another example: the profile’s competitor list includes a company the team now partners with. The editor removes that competitor and adds a writing instruction to avoid framing the partner as a rival. This is an editorial decision, not a documented vendor guarantee about how the AI will interpret the instruction.

Limits

Brand Knowledge is one per workspace, according to the vendor documentation. That means you cannot maintain separate profiles for different product lines within the same workspace without using separate workspaces. The vendor also documents that if you removed Brand Knowledge from a default workspace, you cannot add it back there; you would need a dedicated workspace (https://docs.surferseo.com/en/articles/12631203-brand-knowledge).

The vendor documents that all AI tools use the current version of Brand Knowledge. If you replace the profile, even older Editors switch to the new one (https://docs.surferseo.com/en/articles/12631203-brand-knowledge). This is a versioning constraint, not a feature you can scope per article. It means profile edits are global within the workspace.

Existing queries created without Brand Knowledge cannot enable it later; you must create a new Content Editor document (https://docs.surferseo.com/en/articles/12631203-brand-knowledge). This is a workflow limit to plan around, not a bug.

The Content Editor documentation describes optimization scores and AI search scores, but these are vendor signals, not Google ranking factors or indexing guarantees (https://docs.surferseo.com/en/articles/5700347-content-editor-overview). Treat them as directional feedback, not proof that a page will rank or be indexed.

Absence of a detection signal is not proof of human authorship. If a tool does not flag AI-generated text, that does not mean a human wrote it. This guide does not make authorship claims.

This article is documentation-based research, not a live API test. I did not verify undocumented behavior, request schemas, or data retention practices. Where the vendor documentation is silent, I mark it as unknown rather than inferring a guarantee.

Final Verdict

Review Brand Knowledge before you rely on it. The vendor documents a setup path, a default-on behavior for new queries, a disable option at the fourth step, and a global versioning rule that affects older Editors. Those are the contract facts. Our suggested process is a three-pass review, a pre-draft checklist, and a conflict rule: the brief wins for the article, and you disable rather than rewrite when the profile is wrong for one piece.

The practical value is not in the auto-generated profile itself. It is in the editorial gate you put around it. If you skip the gate, you risk letting a legacy term or a misclassified competitor shape a draft that carries your brand. If you run the gate, you catch those issues before they reach the reader.

Use the checklist. Record your exceptions. Keep the profile current when your business changes, but do not edit it silently for a single article. And remember that optimization scores are vendor signals, not ranking guarantees.

Official Sources

Surfer Brand Knowledge: https://docs.surferseo.com/en/articles/12631203-brand-knowledge
Surfer Content Editor Overview: https://docs.surferseo.com/en/articles/5700347-content-editor-overview
Related background: /surfer-seo-review/