The product, in detail
Explore Awesome.Digital integrations with Google Search Console, GA4, Business Profile, Bing, GitHub, BigQuery, hosted MCP, and operator services for media, outreach, analytics, and advertising.
Showing 21 integrations
No matches. Try another term or clear the filters to browse every category.
Connect authorized properties to the website record. Data reads, management actions, and report inclusion have separate permissions.
In app
Connect a property for search queries, pages, clicks, impressions, positions, device and country breakdowns, and available daily history.
Output: Search evidence for topic mapping, content decisions, reports, and comparisons over time.
Scope: Requires authorized property access. Stored query and page history depends on collection coverage; data already outside Google’s available window cannot be recovered.
In app
Connect a GA4 property to review traffic, pages, sources, events, and available conversion evidence.
Output: Analytics context beside search, audit, and reporting evidence.
Scope: Use the intended property and granted scopes. Historical depth, source freshness, and event configuration affect what can be measured.
In app
Connect eligible locations for local profile and review evidence, including multi-location provenance.
Output: Local context for audits, listings review, and connected local report sections.
Scope: Requires authorized linked locations. A missing connection is not proof of poor local performance.
In app
Bring available Bing search and imported AI citation observations into the record.
Output: A separate search source and dated citation evidence.
Scope: Connection, snapshot availability, and observation windows apply. Imported citations are different from a new model-check run.
Use the product’s evidence and supported tools from an agent, while keeping the same record and permission boundaries.
In app
Create and revoke personal access for supported API or command-line workflows. Keep work scoped to the records and actions you are allowed to use.
Output: Agent-assisted research and execution with token activity and receipts.
Scope: Account → Agent access is live. Choose the appropriate token use and access level. Plan usage and human confirmation requirements still apply; the operator CLI has a broader surface than hosted MCP.
Limited rollout
The hosted server provides an enabled tool catalog to compatible MCP clients using a personal MCP token.
Output: A connection to Awesome.Digital records and supported actions from your own agent environment.
Scope: The server and protocol are live. The setup page documents Claude Code. Client verification, Claude app sign-in, and directory approval remain unverified; hosted Search Console, GA4, and content-opportunity reads are not yet enabled. Do not assume full CLI parity.
Some services supply evidence or power platform data operations rather than appearing as a customer Connect button.
Operator-assisted
The analytical warehouse receives incremental exports of supported snapshots, page facts, indexing observations, query snapshots, and event data.
Output: Warehouse-backed data operations and export evidence for longer-running analysis.
Scope: BigQuery is live in the platform. Export coverage and rebuilds must be verified; customer-owned warehouse delivery is not promised as a self-serve connector. Collected history is not a guarantee of complete or unlimited retention.
In app
Add supporting evidence to a record’s reporting workflow when it is supplied as a file rather than a direct connection.
Output: Source material for a report or evidence review.
Scope: Uploads remain subject to record access and human interpretation. Importing a file does not verify its claims.
Operator-assisted
Supported research uses keyword, search-result, ranking, backlink, and AI-mention evidence from this data service.
Output: Provider-sourced research to combine with the website’s own observed data.
Scope: A research provider, not a promise of an unrestricted customer account connector. Usage, geography, dates, and estimate provenance must be checked.
In app
Different collection paths sample answers or check brand citations. The free preview uses Google AI Overview, Google AI Mode, Bing Copilot, ChatGPT, and Claude when available; paid citation checks use their configured model set.
Output: Dated answers and source observations for the selected questions.
Scope: These are answer-research sources, not a claim of approved agent-directory integrations. Engine sets differ by workflow and plan. The free preview never uses Grok; founding plans exclude it from citation checks.
A working connection, a reviewed publishing action, and a verified deployment are different steps.
In app
Connect the website repository to inspect content and publish through supported commits, branches, and pull requests.
Output: Reviewable site changes, content inventory, and publishing records.
Scope: Requires repository and record access, configured content paths, and included features. Confirm the live deploy after merge.
Operator-assisted
Use GitHub content inventory and the supported future-frontmatter-date pattern with a scheduled deployment.
Output: Content calendars, refresh candidates, and scheduled-site handoffs.
Scope: Scheduling requires the website’s deployment workflow. Astro support does not mean every CMS has the same publishing behavior.
Coming soon
Connection and metadata work exists for WordPress, including categories, tags, images, slugs, and content format handling.
Output: A prepared destination for the forthcoming publish path.
Scope: The in-app and MCP publishing actions return a coming-soon response. Do not rely on live WordPress publishing yet.
Operator-assisted
Submit eligible changed URLs after verifying the IndexNow key hosted on that website.
Output: A notification receipt from the supported submission workflow.
Scope: Requires a valid matching site-hosted key. A successful submission does not establish indexing or rankings.
These are scoped production or operator connections, with provider-specific approvals and readback.
Operator-assisted
Schedule approved social and media work through supported operator paths, then reconcile the provider’s result.
Output: Scheduled posts and scheduling confirmations. Publer remains the provider composer and calendar.
Scope: The general adapter is pilot-proven for LinkedIn, Facebook, and YouTube. A separate approved brand-film path has also scheduled Instagram and TikTok. Support must be checked for the exact format and account; this is not universal all-channel publishing.
Operator-assisted
Use the operator media-production workflow to create voiced narration alongside a mixed music bed.
Output: Audio incorporated into supported video and media renders.
Scope: Production voice setup, rights, usage, and review apply. It is not an unrestricted voice-generation tool included in the free check.
Operator-assisted
Bind a sending connection for supported earned-authority campaigns, preview the intended action, and reconcile provider events.
Output: Approved outreach with delivery, reply, and suppression evidence.
Scope: Earned-placement access and record binding are required. A signed-in person confirms and starts sending; an agent cannot perform that confirmation.
Operator-assisted
Use record-bound operator reads for contacts, conversations, campaign evidence, workflows, appointments, and form submissions, plus supported provider-outcome reconciliation.
Output: CRM and follow-up context tied to the same business record.
Scope: Provider scopes and available data apply. The general social/email distribution handoff is dry-run-only; read access does not authorize a send, workflow enrollment, or unrestricted CRM write.
Advanced account changes belong to a scoped operator workflow with explicit live-action approval.
Operator-assisted
Inspect bound containers, plan and stage supported changes, and use the version/publish/verify workflow.
Output: Tracking configuration evidence and approved write receipts.
Scope: Container binding, Google scopes, and confirmation gates apply. A connected Google identity does not by itself authorize publishing.
Operator-assisted
Read bound account performance and use supported operator broker actions for explicitly approved work.
Output: Advertising evidence and receipts for authorized changes.
Scope: Account binding and Google permissions are required. This is an operator capability, not an all-purpose self-serve ad manager.
Coming soon
A separate operator channel has implementation work for identity, reads, and controlled changes.
Output: A future activated account workflow.
Scope: Current product state lists the channel as inactive pending production setup. It is not marketed as a live customer integration.
Run a free check, then use your report to discuss the data connections, agent access, content work, or reporting your business needs.
Check My Site Free →