Omegro AEO Setup Guide

Hi Tanya,

This guide was reconciled on 21 September against the later AEO, vertical, analytics, podcast and website conversations.

The current public verticals are Asset Management, Equipment Rental, Facilities, Fleet and Marine. Use Facilities Management and Fleet Management when describing the software category in a sentence.

Several original setup items are already live. The remaining work is mainly approval, consolidation and consistent use of the same facts. Do not paste another schema block where one already exists.

How to read the colours

Green = your job, ready to goYou can do this now. Follow the steps and paste the code.

Yellow = check first, low priority, or on holdRead the note. Some of these you only check, some you skip for now.

Blue = Scott is handling itContent or strategy work I am doing. Listed so you can see what is coming.

The full pictureAll 20 items and who does what

Every point from the audit is here. The detailed steps for each are further down.

#	Item	Who	In one line
Part 1 — Quick technical fixes
1	Turn on the site map	Done	The sitemap is live. Recheck it whenever pages are added or removed.
2	Submit site map to Google & Bing	Done	Submitted. Resubmit after material architecture changes and validate any reported fixes.
3	Canonical tags	Verify	Keep one self-referencing canonical per page and repair the podcast Resources binding.
4	Company information code	Consolidate	Keep one canonical Organization entity and add the five verticals to it.
5	robots.txt	Done	The live file is working. Keep one no-www sitemap line.
6	Visible FAQ + FAQ schema	Approved, stage it	All wording approved 21 September. Show the final set on the page, then bind one schema block to it.
7	Vertical information	Scott corrects	Use Organization `knowsAbout`, not Service schema, for the five verticals.
8	Breadcrumbs	Consolidate	Keep one no-www BreadcrumbList per inner page. Do not layer on duplicates.
9	llms.txt file	Skip	Leave for now. Scott will advise if it becomes worthwhile.
Part 2 — Content pages
10	Acquisition Process page	Live	Page is live. Reconcile its visible FAQ and structured data.
11	Founder / About You pages	Live	Pages are live. Keep claims aligned with Lynne's approved answer set.
12	Founder success stories	Scott + Omegro	Omegro gathers 2 or 3 approved stories. Scott shapes them so AI can quote them.
Part 3 — Authority & ongoing
13	Blog / insights section	You run, Scott advises	You own it long-term. Scott helps pick topics and angles.
14	Trade press coverage	Scott	Scott handles this. What's needed from Omegro is outlined below.
15	Press releases link back	You	From now on, every press release links back to the acquisition pages.
16	Claim Glassdoor profile	Low priority	Only worth doing if staff would leave reviews. Skip otherwise.
17	Monthly AI visibility check	You	Use the same questions each month and record the cited page or source, not only the mention.
18	Search Console monitoring	You	Check acquisition-related searches and the Generative AI performance report monthly.
19	Track AI referrals & citations	Manual baseline	Use GA4, Search Console, Lead Forensics and a manual citation log on the standard Webflow plan.
20	Ongoing FAQ expansion	You run, Scott advises	Add new questions and answers as real founder enquiries come in.

One thing to check first. To paste code into Webflow, the site needs to be on a paid Webflow plan. If you are not sure, just try the steps. If you cannot find a code box, tell me and we will sort it.

Your progress 0 ticked

Tick each item below as you go. Your progress is saved on this device, so you can close the page and come back to it.

Part 1Quick technical fixes — yours to do

Small, safe changes. Most take a few minutes each. Work down in order.

Turn on the site map

5 minutes

What this does

A site map is a list of every page on the website. It helps search engines and AI find them all. Webflow can build this list for you. You just switch it on.

Where to go in Webflow

Open Site Settings → SEO tab → Sitemap section.

Steps

Log in to Webflow and open the Omegro project.
Click Site Settings.
Click the SEO tab.
Switch Auto-generate sitemap to ON.
Click Save, then Publish (top right).

To check it worked, type your website address then /sitemap.xml into a browser. If you see a list of pages, it is working.

Tick when done

Tell Google and Bing about the site map

15 minutes

What this does

Once the site map exists, you hand it to Google and Bing so they know where to look. It also gives you free reports later.

Steps for Google

Go to Google Search Console and sign in with a company Google account.
Add the Omegro website if it is not there yet (Google gives you instructions to prove you own it).
On the left menu, click Sitemaps.
Type sitemap.xml and click Submit.

Steps for Bing

Go to Bing Webmaster Tools and sign in.
Add the website (you can import straight from Google to save time).
Find Sitemaps and submit sitemap.xml.

Tick when done

Verify the canonical tags

After changes

What this does

A canonical tag tells search engines which version of a page is the main one. The live site has canonicals, but the podcast Resources copy needs its CMS binding repaired so the intended value reaches the rendered page.

How to check

Open the Omegro website in Google Chrome.
Right-click on the page and choose View Page Source.
Press Ctrl + F (or Cmd + F on a Mac) to search.
Type canonical and press Enter.
If it finds a line with "canonical", you are done. Tick this off.
If it finds nothing, note it and tell me. I will send the exact code.

Do not add any canonical code yet. We only add it if the check finds none. Adding it when Webflow already does it can cause problems.

Tick when checked

Consolidate the company information code

Scott supplies

What this does

The site already has Organization schema. The job is to keep one canonical entity, not paste another copy. The final object should use https://omegro.com, Omegro's approved description and profiles, and the five current verticals from item 7.

Do not add another block. Scott will return one complete replacement after the current duplicate Organization declarations have been reconciled.

Tick when one canonical Organization entity is live

Update the robots.txt file

5 minutes

What this does

A simple setting that gives AI and search engines permission to read the site. The live file is working; keep the no-www sitemap line and recheck it after domain or publishing changes.

Where to go in Webflow

Open Site Settings → SEO tab → the robots.txt box.

Steps

Copy the text below.
Go to Site Settings → SEO → robots.txt and paste it.
Check the last line matches your real web address (see the yellow note).
Click Save, then Publish.

User-agent: *
Allow: /

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

Sitemap: https://omegro.com/sitemap.xml

Quick check. Look at the last line. Make sure the address matches the real Omegro website exactly. If your address has no "www.", remove it from that line too, so they match.

Tick when done

Reconcile the visible FAQ and its schema

Approved

What this does

The Acquisition Process page already has FAQ schema, so do not paste another block. Its questions and answers must also appear visibly on that page.

Core questions for Lynne to approve

What types of software companies does Omegro acquire?
What size companies does Omegro acquire?
What happens to a company after acquisition?
Does the brand and leadership team stay in place?
Does Omegro sell the businesses it acquires?

Approved by Lynne on 21 September. The five verticals are final, all public dollar references must be removed, permanent ownership or "never sells" is acceptable, and 1,200-plus acquisitions may be used when attributed to Constellation Software. The qualified leadership wording (leadership structures may evolve where needed) was also confirmed the same day.

One source only. The live page currently has nine schema questions. Merge those with the five questions above, remove duplication, place the approved answers visibly on the page, then bind the same text to one FAQ schema block.

Tick when Lynne has approved the source answers

Add the five verticals to the Organization entity

Scott supplies

What this does

The verticals describe the software businesses Omegro acquires. They are not services that Omegro sells, so separate Service objects are the wrong model.

Fragment to merge into the existing Organization object

"knowsAbout": [
  "Enterprise Asset Management software",
  "Asset Management software",
  "Equipment Rental software",
  "Facilities Management software",
  "Fleet Management software",
  "Marine software"
]

Do not paste this as a new script. Scott will return one complete, corrected Organization block after the existing duplicate Organization declarations have been consolidated.

Tick when the consolidated Organization block is live and verified

Add the page path code (breadcrumbs)

10 minutes

What this does

Shows AI how a page sits inside the website, like a trail (Home → About). A small helper. Least important item on the list.

Where to go in Webflow

Same as item 7: the page's gear icon → Custom Code → Inside <head> tag.

Steps

Copy the code below.
Paste it into the page's Inside <head> tag box.
Change the yellow parts to the page name and address.
Click Save, then Publish.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://omegro.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "NAME OF THIS PAGE",
      "item": "https://omegro.com/PAGE-ADDRESS-ENDING"
    }
  ]
}
</script>

Before adding anything. Search the page's code for BreadcrumbList. If one exists, correct and consolidate it rather than adding another. Omegro's canonical format is the no-www address shown above.

Tick when one no-www breadcrumb block remains

The llms.txt file — skip for now

On hold

What this is

The audit suggested a file called llms.txt. It is a very new idea, not properly supported on Webflow yet, and no major AI tool has confirmed they use it. It is also awkward to set up.

My advice: skip this for now. The effort is not worth it at this stage. I will watch it, and if it becomes worthwhile I will come back with a simple way to do it. Please do not spend time here.

Noted, skipping

Part 2Content pages — live, now keep them aligned

The Acquisition Process and About You pages are live. The remaining job is to keep their visible copy, metadata and schema tied to one approved source of truth.

Acquisition Process page & (11) About You pages

Live, reconcile

The pages now explain the acquisition process and speak directly to founders and other decision-makers. Use them as the visible source for the FAQ, not as a separate version of the story.

Approved treatment

Target size: keep the public answer qualitative and remove every dollar reference.
Permanent ownership: either "permanent ownership" or "never sells" is approved.
Brand and leadership: preserve the brand, culture, customer relationships and people, while qualifying that leadership structures may evolve where required for long-term growth. Approved by Lynne on 21 September.
Acquisition count: more than 1,200 is approved when clearly attributed to Constellation Software.

Required removal. Lynne instructed the team to remove every public dollar reference, including the live homepage statement of $4M+ USD revenue and recurring revenue above $2M USD.

After approval. Update the visible page first, bind the same answers to the schema, then verify the rendered page and structured data before closing the item.

Founder success stories

Omegro supplies, Scott shapes

Short, real stories from founders whose companies Omegro acquired are some of the most convincing, quotable content AI can find. Competitors use these well.

What is needed here. Build toward at least one approved story for each of the five verticals. Each story needs a vertical field, region, business unit, approved facts and explicit publication permission. Keep the vertical as CMS metadata, not in the URL path.

Part 3Authority & ongoing — mostly yours to own

These build Omegro's reputation over time, which is the biggest driver of AI visibility. I give the direction, you run most of them day to day.

Blog / insights section

You run, Scott advises

Regular articles on acquisition and founder topics build authority steadily. Plan topics against the five current verticals so Asset Management, Equipment Rental, Facilities, Fleet and Marine all develop useful proof instead of becoming labels with no supporting content.

For every YouTube upload, including podcast episodes. Add tags, a full description, chapters, and the transcript in the video's caption track. AI tools pull directly from YouTube descriptions and transcripts when they answer questions about a company, so this is worth doing every time. (Added 25 September, as promised on 28 August.)

Ongoing

Trade press & industry coverage

Scott handles

Getting Omegro mentioned in EAM and M&A industry press is one of the strongest ways to get named by AI, because AI leans on what other trusted sources say. This is part of the strategy work I am already doing, so there is nothing for you to action here.

What this needs from Omegro (for context, not action from you)

Confirmation of who is authorised to be quoted on the record, most likely Troy or Lynne, and roughly what they are comfortable saying publicly.
An early heads-up when something newsworthy happens, an acquisition, a leadership change, a milestone, so I can pitch it to trade press while it is still timely.
A fast internal sign-off path. Trade journalists often want comment within 24 to 48 hours, so someone needs to be able to approve a quote quickly.

With Scott

Link press releases back to the acquisition pages

Ongoing habit

A simple habit going forward. Whenever a press release goes out (for example on GlobeNewswire or Yahoo Finance), include a link back to the acquisition or founder page on omegro.com. This passes credibility back to those pages.

What to do. Add this as a checklist step for whoever writes and sends the releases. No technical work, just a habit.

Add to release checklist

Claim the Glassdoor profile

Low priority

The audit suggested claiming a Glassdoor employer profile. This is only worth doing if Omegro has enough staff who would actually leave genuine reviews. It has little to do with acquisition-related AI searches.

My advice: only do this if it is quick and there are people who would review. Otherwise skip it. Low priority either way.

Decide and note

Monthly AI visibility check

Yours, monthly

Once a month, re-run the same questions through the AI tools. Keep the wording, location and signed-in state consistent so the comparison is useful.

What to record. Note whether Omegro appears, the exact Omegro page or third-party source cited, the answer position and any incorrect fact. A mention without the cited source is not enough to diagnose what changed.

Set a monthly reminder

Watch the Search Console reports

Yours, monthly

Once Search Console is set up (item 2), check it monthly for searches about acquiring or selling software companies. Also use the Generative AI performance report to track AI-search impressions by page, country, device and date.

Check monthly

Track AI referrals and citations

Manual baseline

Omegro is on a standard Webflow plan. That provides AI-referral visibility but not the enterprise prompt tracking, citation rate, visibility score and LLM bot reporting discussed in the analytics thread.

Practical measurement set: use the monthly question log, Google Search Console, GA4 AI-referral traffic and Lead Forensics. Do not buy the standard add-on expecting enterprise AEO reporting.

Baseline and cadence recorded

Grow the FAQ over time

You run, Scott advises

As real founder enquiries come in, add them to the single approved answer source first. Update the visible page and its schema together so the two versions never drift.

Ongoing

Reconciled additions to the working checklist

From later threads

Vertical consistency: every page, story, episode and press release uses one of the five current verticals as CMS metadata.
Visible-answer gate: only mark up FAQ answers that visitors can read on the same page.
Proof by vertical: build toward one approved customer or founder story for each vertical.
Podcast and YouTube: use descriptive titles, summaries, speaker identity, key takeaways, show notes, transcripts and correctly separated PodcastEpisode and FAQ schema.
Claim log: record the source, approver and review date for financial, acquisition-count, ownership, brand and leadership claims.
Quarterly review: recheck the taxonomy and approved answers so older wording does not return through reused content.

Finished, or want me to take a look?

When you have worked through the items you can, click below. It opens an email to me with a list of what you have ticked and what is still open, so I know where things stand. Change or add to it before you send.

Let Scott know where I'm up to

No email app set up? Just reply to me on our usual thread and let me know you are done. Either works.

Helpful to knowSimple word list

AEO (Answer Engine Optimisation): Getting a business mentioned when people ask AI tools questions, such as ChatGPT or Google's AI answers.
Schema (or "structured data"): Small pieces of code that describe a page in a way machines understand. It does not change what visitors see.
Site map (sitemap.xml): A list of all the pages on the website, used by search engines to find everything.
robots.txt: A short file that tells search engines and AI what they are allowed to read.
Custom Code / Head Code: A box in Webflow where you paste small pieces of code. You do not write it, you only paste what I give you.
Publish: The Webflow button that makes your changes go live. Nothing takes effect until you Publish.