AumViso

SEO and GEO in one place: the tags search engines read, the structured data they parse, the sitemap they crawl, and the llms.txt file AI assistants look for.

This guide is for people who already have AumViso installed. Everything below is in the WordPress admin under AumViso.

The AumViso admin is in English on every site. No translation has been published for it yet, so the labels quoted here are what you will see whatever language your WordPress is set to.

1. What AumViso does, and how the pieces fit

Two jobs, one plugin.

SEO is the older job: give each page a title and description, mark it up so a search engine knows what kind of thing it is, list every page in a sitemap, and link related pages to each other.

GEO is the newer one. AI assistants do not crawl a site the way a search engine does. They want facts they can quote, in a form they can read without guessing. AumViso writes those facts three ways: as structured data in the page, as a plain-text llms.txt at the root of the site, and as content types built for the purpose — FAQs, a glossary, and step-by-step guides.

The two jobs share one idea: say what you are, in a form that does not need interpreting. Everything in the plugin is some version of that.

Knowledge in AumViso comes in two layers, and the distinction matters because several screens refer to it:

• First layer — facts only you know. Your company identity, your products, your glossary terms. Nothing can generate these; you supply them.
• Second layer — material built from the first layer. FAQs and guides that answer questions using facts already on record.

The Knowledge Builder screen exists to turn the first layer into the second. It cannot run before the first layer has something in it.

2. Installing and the first ten minutes

Install and activate as usual. A new AumViso item appears in the admin menu.

AumViso does nothing to your site on activation. It does not change your titles, your URLs or your theme. Nothing is written to the front end until you turn a feature on.

Open AumViso → Setup. That screen does two things: it draws how the pieces fit together, and it lists the next steps in the order they make sense. If you do nothing else, do these three:

1. Brand Entity — who you are. Five minutes.
2. Technical SEO — title and description templates, and which post types get SEO fields. Ten minutes.
3. llms.txt — one switch, then a description.

Everything after that is optional and most of it costs money to run, because it calls an AI provider.

2.1 Does AumViso replace my other SEO plugin?

It covers the same ground, so running two of them means two sets of meta tags in your <head> and two sitemaps. Pick one. If you are migrating, turn the other one off first and check your source for duplicate tags.

3. Brand Entity

AumViso → Brand Entity. This is first-layer knowledge: facts about the organisation that nothing can infer.

Below those, the same screen takes a longer description, a slogan, a founding date, founders, social profile URLs (one per line), an email, a phone number and a postal address.

Fill in what is true and leave the rest empty. Blank fields are omitted from the structured data. A field filled with something approximate is worse than a missing one — it is a statement you did not mean to make.

4. Technical SEO

AumViso → Technical SEO. Five sections — Meta, Schema, Sitemap, Robots.txt and Internal Links — reachable from the row of chips at the top, with one Save Settings button. Saving runs all five, and each section writes only its own settings, so there is no need to visit them one at a time.

The screen opens with a line worth taking seriously: A template arrives with all of this configured. Change it only if you know why.

4.1 Meta

SEO title template and Meta description template are the defaults used for any page that has no title or description of its own. The variables are listed under each field: {post_title}, {site_name}, {category}, {author}, {year} and {sep} for the title, and {post_excerpt} for the description.

OG fallback image is used when no featured image and no OG image is set.

4.2 Enable SEO fields for

Check a post type to enable it, then choose which levels get SEO fields: Single, Archive and Tax archive have their own column. Enabling a type adds the AumViso box to its editor (see section 7).

Leave the types you never optimise unticked — it keeps the editor clean and keeps those pages out of several reports.

4.3 Schema

Site-wide structured data, built from what you entered in Brand Entity. Per-page overrides live in the editor box.

4.4 Sitemap

AumViso writes an XML sitemap and a matching index. Included content decides which post types and taxonomies appear in it.

A page in the sitemap but marked noindex is a contradiction a search engine will notice. If you exclude something from indexing, exclude it here too.

4.5 robots.txt

AumViso can serve a robots.txt for the site. If a real robots.txt file exists in your web root, that file wins and WordPress never gets asked — AumViso cannot override it. Delete the file if you want the plugin to manage it.

4.6 Internal Links

The keyword table lives here, not on the Linking & Related screen. Each row is a Keyword, a Target URL, Max links per page and a Case sensitive switch, with a Delete button; Add keyword below adds one.

The switch that turns linking on, and the post types it applies to, are on the other screen — see section 6.1.

5. llms.txt

AumViso → llms.txt. llms.txt is a plain-text file at the root of a site that tells an AI assistant what the site is and what is worth reading. It is a young convention, not a standard, and assistants that do not know about it simply ignore it.

The screen links to the live file above the settings, so you can read exactly what a visitor would get. Two are served: /llms.txt (the list) and /llms-full.txt (the same, with excerpts).

No file is written to disk. Both are generated per request and always reflect your current content, which also means they need pretty permalinks — if you get a 404, open Settings → Permalinks and press Save once.

Entries with no answer still appear. If you create an FAQ and leave the answer blank, llms.txt lists the question with nothing after it. Fill them in or unpublish them.

6. Linking & Related

AumViso → Linking & Related.

6.1 Internal linking

This screen holds Enable automatic internal linking and the post types it applies to. The keywords themselves are added under Technical SEO → Internal Links (section 4.6) — the switch and the list live on different screens, which is worth knowing before you go looking for one on the other.

With the switch on, when a keyword appears in content of a chosen post type, AumViso turns the first occurrences into links, up to that keyword's maximum.

Apply to post types limits where this happens. The rewrite is done on output — your stored content is never modified, so turning the feature off restores the original text exactly.

Keep the maximum low. Two or three links to the same place on one page is the point at which it starts reading like spam.

6.2 Related content

Appends a block of related items to the bottom of a post. The number shown and the types considered are set here.

7. The AumViso box in the editor

For every post type ticked in section 4.2, the editor gets an AumViso box.

Shops get two extra fields, price and currency, which feed the product structured data.

The box also shows a score for the page — a read of how complete the SEO and GEO fields are. It is a checklist, not a grade: it tells you what is missing, and missing things are not always wrong. A short utility page does not need a long description.

8. FAQs, Glossary and Guides

Three content types AumViso registers, each with its own menu item.

8.1 FAQs

An FAQ is a question and an answer, optionally with related questions. They can be grouped with the FAQ category taxonomy, and they feed both the FAQPage structured data and llms.txt.

8.2 Glossary

A glossary term has a short definition and a longer explanation, and can point at related terms. Terms are first-layer knowledge — they say what you mean by a word, which is exactly the kind of thing an assistant cannot infer.

A published glossary term can also feed the internal-linking keyword list, so the term links to its own definition wherever it appears.

8.3 Guides

A guide is a sequence of steps, with optional tools, materials, time and difficulty. It produces HowTo structured data and the [aumviso_guide_steps] shortcode renders it.

9. Shortcodes

Six, usable in any content:

If you are following an older copy of this list, check the names. These names changed in an earlier release and documentation written before that change used aum_ instead of aumviso_. A shortcode that is not registered renders as nothing at all, with no error — so an old name looks like a blank space on the page.

10. AI Tools

AumViso → AI Tools. Everything in sections 11 to 13 needs this configured first: a provider, an API key and a model.

The key is stored in your database and sent only to the provider you choose. AumViso makes no AI calls on its own — every call is one you started by pressing a button on one of those screens.

These calls cost money, charged by your provider, not by us. The batch screens can make a lot of calls in one run. Start with a handful of items.

11. Knowledge Builder

AumViso → Knowledge Builder. Builds second-layer FAQ and Guide drafts out of first-layer facts: company facts, products, categories and confirmed glossary terms. You can type the topic and notes yourself, or have them filled in from what is already on record.

Everything it makes is a draft. Read it before publishing — it is written from your facts, but it is still written by a model.

12. Automation and Optimize Existing

Automation shows the state of your knowledge base and what can be kept up to date without being asked each time.

Optimize Existing generates SEO and GEO content across many items at once, in small batches, with a live progress log. Use it on an established site where most posts have no description. Check a few results before letting it run to the end.

Both screens tell you plainly when no AI key is configured, and do nothing until one is.

13. Images

AumViso → Images. Two independent features.

Auto featured image adds a featured image when a draft is generated, so generated posts do not land without one.

AI image generation picks the source: a provider you pay for, or a free one. A generated image is still an image you are publishing — look at it first.

14. GEO Console

AumViso → GEO Console. A live read of how AI-ready the site is, across every piece of content, using the same per-post analysis as the editor score.

Across the top: an average score with a word for it, Content scanned, Missing meta description, Missing featured image, and Products in catalog. Below that, a Score distribution bar — Great (80+), Good (60–79), Average (40–59), Poor (<40) — then a table of published and scanned counts with an average score by content type, and a Product sources note saying whether a catalog was detected.

Treat the average as a direction, not a target. The useful parts are the counts of what is missing, because each one is a list you can go and work through. Refresh at the bottom re-scans; the time of the last scan is shown beside it.

15. Settings reference

16. Troubleshooting

A shortcode shows nothing. The name is probably the old one. See section 9.

My robots.txt changes do nothing. A real robots.txt file in the web root takes priority over anything WordPress serves. Delete it.

/llms.txt returns 404. Most often pretty permalinks: open Settings → Permalinks and press Save once — the plugin's own screen says this too. Otherwise the switch in section 5 is off, or a caching layer is still serving an older 404.

Two meta descriptions in my source. Another SEO plugin is still active. See section 2.1.

An AI screen says nothing happens. No API key. Section 10.

The sitemap is missing a post type. Check Included content in section 4.4 — it is a separate list from the SEO-fields list in 4.2, and a type can be in one without being in the other.

Something I typed into an FAQ did not save. Update to 2.0.18 or later. In 2.0.17 the meta fields on FAQs, glossary terms and guides were never saved, with no error shown. If you lost work that way, it was not something you did.