TriRank setup and evidence guide

Connect a site, distinguish Google Search Console performance from AI citation observations, review SEO tasks, and publish content drafts with TriRank.

Start with the right evidence

TriRank combines two different sources. Google Search Console reports Google search clicks, impressions, click-through rate, and average position. AI citation observations record whether a supported engine cites your site for a tracked question. Connecting Search Console does not turn Google performance into an AI citation measurement. Read the methodology before comparing those results.

You can begin with the free website audit or a public browser tool. A public check is different from a paid monitoring plan: inspect the scope and any usage limit displayed in the tool. A missing or failed observation is not proof that an engine never cites the site.

Choose your first task

Your task	Input and starting point	What you receive
Check a brand once	Enter a brand and domain in the AI visibility checker; review its displayed daily limits and verification step	A dated snapshot with engine answers, source links and unavailable states. It is not continuous monitoring or proof of visits. No Search Console connection is needed for this public check.
Watch buyer questions over time	Sign in, add your own site in Sites, then review AI visibility and your plan's question and probe allowance	Saved observations for the questions you track. Search Console is a separate connection for Google performance; it does not supply AI answers. Missing or failed checks stay unknown.
Decide what to change	Open Actions for your site and inspect the dated evidence	A suggested task to qualify, a draft to review where available, and a record to follow up. A suggestion does not publish a change or guarantee an outcome.

For Google AI Overviews, the tracker provides a dated public example and access to your own saved history after sign-in. Its public form does not run a free live search. Choose the actual measurement you need before purchasing a plan.

Understand costs and access before connecting

Software subscriptions: compare the current site, question, probe and content allowances on Pricing. Content credits and the one-time check-pack balance are different; a check pack does not buy article generation or an ongoing subscription.
Manual work: an audit or directory submission service is a separate order with its own scope. Read the deliverables and terms; purchasing a service does not automatically grant software credits or guarantee a third party's approval.
API and MCP: the public read API returns stored domain signals within its read limits. MCP is a separate, authenticated read-only interface. Read each tool's limits: read-only does not mean every tool is an offline lookup.
Cancellation and refunds: the terms explain subscription cancellation and the first-payment refund window, plus separately ordered service conditions. For help with an order, contact support; never include an API key, password or full card number.

Connect a site

Sign in and open Sites. Add a site that you control.
Start the Google Search Console connection from the site workflow. Choose the Google account that has access to the intended property and review the requested permissions.
Select the correct property. Domain properties and URL-prefix properties have different coverage; the property must match the site you intend to analyze.
Wait for the data pull and read its actual status. An empty report can reflect an unfinished pull, limited property history, or a date range with no records. Check the displayed dates before treating it as a result.

Monitor questions and act on findings

Choose questions that a potential customer would actually ask. Review the supported engines and the allowance displayed for your plan before adding more tracking. Keep the question, engine, observation date, and cited URL together when interpreting a reading. Search Console positions are average Google positions, not a ranking inside an AI answer.

Use the findings to prioritize a specific SEO task. Review sources, factual claims, and internal links in any generated draft before publishing. When using the Shopify connector, verify the article in Shopify Admin as a draft before deciding to publish it. Generating content and publishing it are separate actions.

Bring stored evidence into other workflows

The MCP integration exposes supported read-only tools for stored evidence. The n8n integration provides workflow templates. Configure your own credentials in the receiving application; never put an API key in a public page or shared screenshot. Check the permissions and output of a workflow before enabling a recurring run.

See pricing for the current enabled plans and allowances. If a connection or pull fails, use Contact with the page, approximate time, and visible error. Do not send passwords or access tokens.

Start with the right evidence

Choose your first task

Your task	Input and starting point	What you receive
Check a brand once	Enter a brand and domain in the AI visibility checker; review its displayed daily limits and verification step	A dated snapshot with engine answers, source links and unavailable states. It is not continuous monitoring or proof of visits. No Search Console connection is needed for this public check.
Watch buyer questions over time	Sign in, add your own site in Sites, then review AI visibility and your plan's question and probe allowance	Saved observations for the questions you track. Search Console is a separate connection for Google performance; it does not supply AI answers. Missing or failed checks stay unknown.
Decide what to change	Open Actions for your site and inspect the dated evidence	A suggested task to qualify, a draft to review where available, and a record to follow up. A suggestion does not publish a change or guarantee an outcome.

Understand costs and access before connecting

Software subscriptions: compare the current site, question, probe and content allowances on Pricing. Content credits and the one-time check-pack balance are different; a check pack does not buy article generation or an ongoing subscription.

Manual work: an audit or directory submission service is a separate order with its own scope. Read the deliverables and terms; purchasing a service does not automatically grant software credits or guarantee a third party's approval.

API and MCP: the public read API returns stored domain signals within its read limits. MCP is a separate, authenticated read-only interface. Read each tool's limits: read-only does not mean every tool is an offline lookup.

Cancellation and refunds: the terms explain subscription cancellation and the first-payment refund window, plus separately ordered service conditions. For help with an order, contact support; never include an API key, password or full card number.

Connect a site

Start the Google Search Console connection from the site workflow. Choose the Google account that has access to the intended property and review the requested permissions.

Select the correct property. Domain properties and URL-prefix properties have different coverage; the property must match the site you intend to analyze.

Wait for the data pull and read its actual status. An empty report can reflect an unfinished pull, limited property history, or a date range with no records. Check the displayed dates before treating it as a result.

Monitor questions and act on findings

Bring stored evidence into other workflows

See pricing for the current enabled plans and allowances. If a connection or pull fails, use Contact with the page, approximate time, and visible error. Do not send passwords or access tokens.