Skip to content

Add Pages and Edit Page Metadata

Published pages and posts can be selected as sources. Each source can carry administrator-authored category, summary, topics, FAQs, key facts, related pages, and exclusion guidance.

Page metadata adds structured context alongside the processed page text. It can tell retrieval what the page is about, which visitor terms relate to it, which facts or FAQs are central, and which internal pages are connected. Metadata improves discovery and interpretation, but it does not replace accurate page content and it is not a permission or redaction system.

The practical starting point is to search the page list and select the intended published sources. Continue through the workflow until you test a question that uses the new metadata, then use the field notes below to understand which choices affected AI output and which only changed delivery, access, or presentation.

Use metadata when the page title/body alone does not express the questions, entities, relationships, or exclusions visitors need.

Use this feature in the following situations:

  • Visitors use different words from the official page title and retrieval misses the source.
  • A long page needs a concise summary, important facts, or common questions highlighted.
  • You want to relate several internal pages or tell the assistant which portions are not useful for answers.
WordPress locationWordPress Dashboard → AI Website Chat → Knowledge Base
  • SmartSite Assistant is installed and activated.
  • You are signed in with an account that can manage WordPress options.
  1. Search the page list and select the intended published sources.
  2. Open a page metadata editor.
  3. Review the automatic title, URL, and content preview.
  4. Enter only accurate Category, Summary, Topics/Keywords, FAQs, Key Facts, Related Pages, and Exclude Content guidance.
  5. Save Metadata; this also selects the page and marks changed content Pending.
  6. Run Sync and wait for a successful result.
  7. Test a question that uses the new metadata.

Metadata gives the AI extra clues about what a page contains and when it is relevant. A clear category, summary, and topic list can help retrieval connect a visitor’s wording with the right page even when the same words are not used. FAQs and key facts surface likely answers more directly, while exclusions reduce unwanted guidance but should never be treated as a security control.

Fields, controls, and important values
Field, control, or statusWhat SmartSite Assistant does with itHow to use it and why it matters
Category Administrator-supplied grouping context. Choose a short subject grouping such as “Shipping,” “Membership,” or “Technical support.” This gives retrieval another clue about the page’s role, helping a question reach the right source when several pages use similar language for different subjects.
Summary Concise description of the source and its purpose. Describe the page’s main purpose and the answer a visitor can expect to find there. A focused summary gives the AI a quick representation of a long page, which can improve matching when the visitor phrases the question differently from the original content.
Topics / Keywords Search concepts associated with the source. Add the concepts, product names, services, and common visitor terms that genuinely belong to this page. These additional ways of describing the same subject can help retrieval connect everyday wording with a source that uses more formal or brand-specific language.
FAQs / Key Facts Structured question-answer pairs and concise factual statements. Capture the questions people are likely to ask and the concise facts that must survive retrieval. Well-written entries give the model direct, structured material for common answers; inaccurate or promotional entries can be repeated just as confidently, so check every statement.
Related Pages Links this source to candidate internal pages. Link pages that provide a useful next step or necessary supporting detail. This context can help the assistant understand how sources belong together and mention a relevant follow-up page, but it should not be used to connect pages merely because they share a broad topic.
Exclude Content Instructions about portions that should not guide responses; verify the result rather than treating this as a security boundary. Describe sections that should not guide answers, such as navigation, outdated notices, or repeated boilerplate. This can reduce distracting context and make the useful part of a page easier to work with, but it is guidance rather than a privacy barrier—remove sensitive text from the source itself.

Judge Add Pages and Edit Page Metadata where its effect is actually consumed—by the administrator, visitor, model, or connected service. The expected result above is more useful than a green badge because it describes the behavior the configuration was meant to produce.

Add alternate visitor terms to Topics for a service whose official page title uses internal terminology.

  • Change one part of Add Pages and Edit Page Metadata at a time and keep a short record of the previous value and test result.
  • Judge the change with a fresh question that depends on this source; an admin status cannot show whether retrieval chose it.
Common problems and focused checks
ProblemWhat to check and what to do next
Add Pages and Edit Page Metadata is missing or does not match this guide. Confirm the plugin is active and the account can manage WordPress options. Check selection, synchronization, remote processing, and retrieval evidence in that order.
A change on Add Pages and Edit Page Metadata does not produce the expected result. Keep the exact notice and test case, then review the browser console and WordPress/PHP log. Check selection, synchronization, remote processing, and retrieval evidence in that order.
Add Pages and Edit Page Metadata
Capture
Open the metadata editor for a fictional published page with every metadata section expanded and safe example values filled in.
Show
Content preview, Category, Summary, Topics, FAQs, Key Facts, Related Pages, Exclude Content, Save Metadata
Viewport
Desktop, 1440 × 900
Annotate
Use numbered callouts only for controls referenced in the procedure.
Redact
OpenAI keys, tokens, secrets, personal information, private URLs, IP addresses, and conversation text