Help Center

GEO Score and domain analysis

Baseline how ready your domain is for generative engines.

GEO Score is MAIO's readiness KPI for how clearly AI systems can understand, extract, and cite your domain. A domain analysis crawls public pages, scores technical and content signals, and produces recommendations. Use it before you start fixing, and again after you ship changes, so progress is measurable.

1. From Home or Dashboard, enter a public URL and run an analysis.
2. Read the overall GEO Score, then open the category breakdown (entities, structured data, content, technical access).
3. Open high-impact recommendations; many map into Action Center as tasks.
4. Share a public report with stakeholders when you need a snapshot without granting product access.
5. Re-run the same domain after fixes and compare scores in History.

Example: analyze your homepage and top product URLs, fix missing Organization schema and thin FAQ pages, re-analyze in two weeks, and show leadership the score delta in History.

Action Center

Turn findings into an owned remediation queue.

Action Center is the work board for GEO. It connects analysis findings (and later Prompt Tracker signals) to concrete tasks. The goal is not a longer report; it is a prioritized list with owners, status, and a clear next fix so SEO, content, and engineering can execute together.

1. Open Action Center after at least one analysis exists for the active domain.
2. Review priority and impact. Start with items that unblock grounding and citations (entities, schema, answer-ready pages).
3. Open an item, read the guidance, implement the change on your website or CMS.
4. Update status when work is done so the queue reflects reality.
5. Re-analyze or re-run Prompt Tracker so measurement catches up with the fix.

Example: this sprint, clear three structured-data tasks on product templates; next sprint, clear content tasks for comparison pages; then re-score and check Prompt Tracker mentions.

Prompt Tracker

Measure how AI models answer real buyer questions.

Prompt Tracker runs your prompts against supported AI models on a schedule. You see whether your brand is mentioned, recommended, cited, or omitted, and how answers change over time. It is the primary measurement layer for AI visibility after GEO Score tells you the domain is ready to be understood.

1. Choose the domain in the workspace switcher, then open Prompt Tracker.
2. Add prompts buyers actually ask (category, comparison, and brand-defense), not only branded vanity queries.
3. Set schedule cadence within your plan limits and confirm models covered by your entitlement.
4. After runs complete, review mention quality, citations, and trends for each prompt.
5. Push weak outcomes into Action Center or content briefs, then re-run to measure lift.

Example: track "best CRM for mid-market field sales" weekly. If a competitor is recommended and you are omitted, publish a grounded comparison page, clear related Action Center items, and watch the next tracker cycle.

Share of Voice

Compare your brand presence to competitors in AI answers.

Share of Voice summarizes how often AI answers mention your brand relative to competitors across tracked prompts. Use it after Prompt Tracker has enough runs. It is a portfolio KPI for leadership, not a replacement for reading individual answers.

1. Confirm Prompt Tracker has completed runs for the prompts you care about.
2. Open Share of Voice and select the domain and time window.
3. Identify clusters where competitors dominate decision-stage prompts.
4. Translate gaps into Action Center or content work (entity clarity, comparisons, proof pages).
5. Re-check SoV after the next tracker cycles; treat short windows as noisy.

Example: SoV looks fine on awareness prompts but weak on "vs competitor" prompts. Brief product marketing for two comparison assets, then reassess SoV in four weeks.

AI Sentiment

See how AI answers frame your brand.

AI Sentiment analyzes tone and framing in tracked answers: positive, neutral, or negative themes. Visibility without narrative control can still hurt pipeline. Use sentiment with Share of Voice so you know both how often you appear and how you are described.

1. Open AI Sentiment once Prompt Tracker has answer samples for your domain.
2. Review themes (pricing, reliability, fit, support) rather than only an average score.
3. Trace negative or outdated claims to cited pages or thin first-party content.
4. Fix substantiation on your domain and high-authority sources when claims are wrong.
5. Re-run Prompt Tracker and confirm sentiment themes improve on the same prompt set.

Example: answers call your product "hard to implement." Update implementation docs, add a clear onboarding FAQ, and re-check sentiment on decision-stage prompts.

AI Web Analytics

Measure AI-related traffic and on-site behavior.

AI Web Analytics connects discovery in answer engines to what happens on your properties. It helps product and SEO teams share one measurement layer for AI-referred or AI-related visits, not only GEO Score points.

1. Connect the domain (WordPress plugin or supported tracking) so analytics can receive signals.
2. Open AI Web Analytics and confirm the active domain.
3. Review trends for AI-related sessions, engines, and top pages.
4. Correlate spikes or drops with content launches and Action Center work.
5. Use findings to prioritize pages that attract AI visits but convert poorly.

Example: after a docs refresh, AI Web Analytics shows more assistant-referred sessions on the pricing page. Improve the pricing FAQ and schema, then watch bounce and assisted conversions.

AI Readiness Badges

Publish a verifiable signal of AI readiness.

AI Readiness Badges are shareable marks you can embed on your website or use in proposals. They communicate preparedness to customers and partners when your score and process meet your internal bar.

1. Complete analyses for the domain you want to badge.
2. Open Badges and generate or manage badges for eligible results.
3. Copy the embed or share link according to your brand guidelines.
4. Place the badge where trust matters (footer, partner page, proposal appendix).
5. Refresh when you re-score and the underlying result changes.

Example: once GEO Score clears your threshold and Action Center P1s are clear, add the badge to the marketing footer and sales one-pager.

WordPress plugin

Automate GEO-oriented optimizations on WordPress.

The official WordPress plugin is the fastest path for WordPress domains to apply GEO-oriented optimizations and connect domain signals into MAIO. You do not need WordPress to analyze a domain, but the plugin reduces manual CMS work.

1. Install from WordPress.org on staging first.
2. Connect the plugin to your MAIO account and verify the domain.
3. Confirm Dashboard and AI Web Analytics begin receiving expected signals.
4. Review plugin settings with your usual release process, then promote to production.
5. Re-analyze the domain after go-live to capture the new baseline.

Example: install on staging, connect MAIO, validate score and analytics, then deploy in a documented change window with a rollback plan.

MCP and API access

Let approved agents call MAIO with tokens you control.

MCP (Model Context Protocol) lets internal agents and tools use MAIO capabilities through tokens you issue and revoke. Use it when you want GEO data inside your own research or ops workflows without handing out full product logins.

1. Read the MCP overview for capabilities and security expectations.
2. From your authenticated account, create a scoped token for a named use case.
3. Configure your agent or tool with the token and least privilege needed.
4. Verify calls against a non-production or low-risk domain first.
5. Rotate or revoke tokens when people, vendors, or agents change.

Example: issue a token for an internal research agent that pulls latest GEO findings into your wiki each Monday.

Team collaboration

Invite seats and keep GEO work owned.

Team collaboration lets multiple people share a workspace: domains, Action Center, and tracker views. Clear ownership is what makes GEO programs move; invitations without roles usually stall.

1. Open Team (collaboration) from the app sidebar.
2. Invite teammates with the right seat type for your plan.
3. Align who owns technical fixes versus content versus measurement.
4. Use the shared Action Center queue so status is not trapped in email.
5. Remove access when contractors or agencies finish engagements.

Example: invite the SEO lead, content owner, and one engineer so every Action Center P1 has a named human owner.

Multi-domain workspaces

Track multiple domains under one account.

Many teams manage brand, regional, or product domains in one MAIO account. Domain switching keeps scores, tracker data, and analytics scoped to the domain you are operating on. Plan limits determine how many domains you can track.

1. Add a domain from Dashboard or the domain switcher according to your plan.
2. Run a baseline analysis on each new domain before inviting the wider team.
3. Use the domain chip or switcher before opening Prompt Tracker or Action Center.
4. Keep naming consistent (prefer canonical hostnames your team already uses).
5. Retire or consolidate domains when brands merge or domains shut down.

Example: add a regional brand domain, switch the active domain, and build a separate Prompt Tracker set for that market's language and competitors.

Account, plans, and billing

Manage profile, plans, SSO, and invoices.

My Account holds profile security, email preferences, and enterprise SSO entry points. Plans and Billing cover upgrades, invoices, and subscription changes. Size seats and domains before a wide rollout so invites do not hit plan limits mid-project.

1. Open My Account to update profile, password, and notification preferences.
2. Compare tiers on Plans before inviting seats or adding domains that exceed your limit.
3. Complete checkout, then use Billing manage for invoices and payment methods.
4. If your plan includes SSO, configure the IdP from My Account with IT.
5. Use Contact with category billing for failed payments or seat adjustments.

Example: upgrade before inviting eight seats, then open Billing manage for the first invoice and finance's vendor onboarding pack.

Earn credits and referrals

Add analysis capacity through referrals when you need it.

Credits power analyses and related capacity on your plan. Referral and earn-credit flows add capacity when you need more runs without waiting for the next billing cycle.

1. Open Earn Credits while signed in.
2. Copy your referral link or complete the listed earn actions.
3. Share the link with partners who will create real accounts.
4. Confirm credited capacity in your credits display after the referral qualifies.
5. Spend credits on additional domain analyses or re-runs as needed.

Example: share your referral with a partner agency; when they activate, apply earned credits to a second brand domain analysis.

GMEC certification

Train and prepare for GEO marketing certification.

GMEC (GEO Marketing Expert Certified) is MAIO's two-level certification for practitioners and strategists. Self-paced training and exam prep are available when signed in. The official timed exam opens with cohort enrollment.

1. Open the GMEC page to compare Level 1 Practitioner and Level 2 Strategist.
2. Sign in, then start training for your level (twelve chapters with examples).
3. Use exam prep (thirty chapter-balanced draws from a 200-question bank) to check readiness.
4. Contact us with category certification for cohort dates and enrollment questions.
5. After certification terms publish, follow the assessment path for your level.

Example: complete Level 1 training in a week, run exam prep until you clear weak chapters, then contact the certification team about Cohort 1 timing.

GEO blogs and education

Long-form education on GEO practice.

MAIO blogs publish longer guides on generative engine optimization, structured data, citations, and related practice. Use them to brief engineering and content before Action Center sprints.

1. Open Blogs and filter or browse by GEO-relevant topics.
2. Share specific posts with owners before a related remediation sprint.
3. Pair reading with a live analysis so advice maps to your domain.
4. Capture follow-ups as Action Center tasks, not as unread tabs.

Example: share a schema guide with engineering the week before an Action Center structured-data sprint.

Recommended enterprise rollout

Pilot one domain, prove lift, then expand.

Enterprise programs fail when every domain and seat starts at once. Pilot a flagship domain, prove GEO Score and Prompt Tracker lift, then expand domains, seats, SSO, and MCP with a clear operating cadence.

1. Pick one revenue-critical domain and run a baseline analysis.
2. Stand up Action Center owners across SEO, content, and engineering.
3. Configure Prompt Tracker for the top buyer journeys.
4. Review Share of Voice and AI Sentiment with leadership.
5. Invite the broader team, add remaining domains, enable SSO if required.
6. Connect MCP for agent workflows and publish readiness badges when thresholds are met.

A 90-day pilot: weeks 1-2 baseline and fixes, weeks 3-6 tracker and content, weeks 7-12 multi-domain expansion.

Enterprise SSO

Connect your corporate identity provider.

Enterprise SSO lets people sign in with your IdP (for example Okta or Microsoft Entra) when your plan includes SSO. IT owns the IdP app; MAIO stores the connection metadata you configure in My Account.

1. Confirm your plan includes SSO, then open My Account.
2. Have IT create the OIDC or SAML application for MAIO.
3. Paste IdP metadata or connection details into MAIO as guided.
4. Test with a small security group before company-wide rollout.
5. Document break-glass access for admins if the IdP is unavailable.

Example: IT creates an OIDC app, you paste client details into MAIO, then pilot with the SEO team security group for one week.

Governance and evidence

Keep an audit-friendly trail of GEO work.

Leadership and risk teams ask for evidence, not screenshots from Slack. History, shared reports, badges, and Contact tickets create a durable trail of scores, decisions, and support interactions.

1. Keep a monthly History export or shared report for the operating review.
2. Record Action Center owners and completion for material remediation.
3. Use public reports when vendors or partners need a snapshot without seats.
4. Publish badges only when internal thresholds are met and documented.
5. Route account-specific issues through Contact so tickets stay searchable.

Example: share monthly GEO Score and SoV snapshots in the operating review pack with Action Center completion rates.

How is GEO different from traditional SEO?

Traditional SEO optimizes for search crawlers and ranking systems. GEO (Generative Engine Optimization) improves how large language models understand, cite, and recommend your brand in AI-generated answers. MAIO complements SEO; it does not replace technical SEO fundamentals.

Which AI engines does MAIO focus on?

MAIO is built for visibility across major answer engines and assistants, including ChatGPT, Gemini, Perplexity, and related large language model surfaces. Prompt Tracker helps you measure those systems with your own prompt set.

What is the correct order to use MAIO features?

Analyze first, save the workspace, review GEO Score, clear Action Center items, connect WordPress if applicable, then configure Prompt Tracker. Use Share of Voice, AI Sentiment, and AI Web Analytics once tracker and domain connections produce data. Scale team, domains, SSO, badges, and MCP after the pilot proves value.

Do I need WordPress to use MAIO?

No. Any public website can run a GEO analysis from the home page. The WordPress plugin is the fastest path for WordPress properties to automate optimizations and connect analytics signals.

How quickly will we see results?

GEO Score and Action Center guidance are available immediately after analysis. AI answer surfaces can take longer to reflect content and entity changes, often on the order of weeks depending on crawl and model update cycles. Prompt Tracker is the way to measure that lag for your brand.

How do enterprise teams collaborate in MAIO?

Use Team collaboration to invite seats, keep a shared Action Center queue, and switch domains in one workspace. For identity requirements, configure enterprise SSO in My Account. Contact support if you need help sizing seats or domains for your plan.

What is MCP used for?

MCP (Model Context Protocol) lets approved agents and tools call MAIO capabilities with tokens you control. Start from the MCP page for the developer overview, then create tokens from your authenticated account workflows.

Where do I manage plans and billing?

Compare tiers on Plans, complete checkout, then manage invoices and subscription details from Billing. If a payment fails or seats need adjustment, use the Contact form with category billing.

How do I get help from MAIO?

Use the Contact form with Technical Support for product issues. You can also join the Discord community for peer discussion. Prefer the Contact form for account-specific or enterprise requests so the team can route your ticket correctly.