FAQ
This FAQ is organized by category so you can jump directly to the answers you need. Expand only the questions relevant to your role to avoid information overload.
Coverage includes: onboarding, rankings and reporting, website audits, reviews and GBP, billing, and account/security basics.
Onboarding & Setup
Most teams can complete initial setup in under an hour if they have website URL, primary service categories, and location details ready. Deeper optimization workflows can then be rolled out in phases.
At minimum: business name, website URL, service area or address details, target city/state, and core keywords. Optional but useful inputs include top competitors and historical ranking benchmarks.
Yes. Multi-location support is built in so you can track each location independently while also monitoring account-level trends and workflow priorities.
No. The platform is designed to surface prioritized actions. You can start with guided recommendations and involve technical resources only for advanced items.
Yes. Agencies can segment work by account and location, and use structured workflows to track implementation and results by client.
Yes. Many teams start with one location and core keyword set, then expand once reporting, workflow ownership, and baseline metrics are stable.
Establish baseline rankings, complete profile and location data, run initial audits, and schedule recurring checks so progress can be measured against a documented starting point.
Assign a primary owner for execution and a reviewer for quality control. This avoids stalled tasks and creates accountability for timeline and outcomes.
Rank Tracking & Reporting
Update cadence depends on your run schedule and plan settings. Most teams monitor recurring intervals and run additional checks when launching major changes.
Yes. The platform focuses on local search outcomes and helps connect map and organic visibility signals to practical business decisions.
Short-term movement is normal. Prioritize trend direction over isolated snapshots and compare rankings with conversion-quality indicators such as lead quality and close rates.
Yes. You can evaluate keyword and visibility differences by location to identify where to replicate wins or fix underperforming areas.
Yes. The data can support executive summaries, weekly performance reviews, and action-based reporting for teams and clients.
Start with high-intent and revenue-relevant terms first, then expand into supporting queries after baseline reporting quality is confirmed.
Yes. Use trend views to isolate persistent low-visibility terms and prioritize pages, profile updates, and internal links that support those queries.
Yes. Keep them segmented so teams can distinguish brand demand from true market-share growth in non-branded local discovery.
Website Audit & Technical SEO
Audits review key local SEO signals, technical health, content quality factors, and implementation gaps that can suppress discoverability or trust.
Yes. Findings are prioritized so teams can work highest-impact items first rather than trying to solve every issue at once.
You can run audits as needed and use repeat checks to confirm whether fixes are actually improving outcomes.
Yes. Local landing page coverage, location relevance, and core trust signals are included in actionable recommendations.
Re-run targeted checks after deployment, compare before/after issue counts, and monitor rankings plus conversion indicators over subsequent cycles.
Run an initial full audit, rerun after major site deployments, and use recurring checks to catch regressions before they impact visibility.
Yes. Focus on issues tied to crawlability, relevance, trust signals, and conversion friction before lower-impact cosmetic items.
No. Many actions are content or configuration level. Reserve developer time for structural issues such as templates, schema logic, or indexation controls.
Reviews & Google Business Profile
Yes. Review workflows are designed to help you assess trust trends and maintain consistent response practices.
Yes. You can evaluate important profile fields and identify alignment gaps that affect local relevance and conversion confidence.
Use a repeatable, compliant request process tied to completed services, then respond consistently with useful, brand-aligned messaging.
Yes. Multi-location configurations can support profile-level monitoring and location-specific action planning.
They can influence both trust and local performance. Strong review quality often improves pre-call confidence and supports better close outcomes.
Aim for a predictable response SLA. Faster, professional responses improve trust signals and customer confidence before first contact.
Yes. Categorizing sentiment themes helps teams identify recurring operational issues and improve conversion quality alongside rankings.
Primary categories, service alignment, business details consistency, media quality, and ongoing profile freshness are typically highest leverage.
Billing, Plans & Limits
Use the billing/settings area in the app to upgrade, manage plan status, or access your billing portal.
Access may be restricted depending on status. Resolve billing to restore full functionality and avoid disruption to recurring workflows.
Yes. Plan changes can typically be made from billing controls; effective timing and charges follow your payment processor rules.
Yes. Each plan can include limits for tracked entities and feature access, so confirm your current allocation in settings.
You can manage cancellation from billing controls. Service behavior after cancellation follows your active billing terms and period end rules.
Plan and feature limits are available in your billing/settings areas so your team can confirm capacity before adding more tracked entities.
Access behavior may vary by billing state and plan limits, but historical data handling follows your account terms and platform retention rules.
Receipts and billing artifacts are handled by your payment workflow. Keep billing contact details current to ensure delivery.
Account, Access & Security
Secure authentication manages account access and protected app routes. If session state expires, you may be asked to sign in again.
Use standard recovery options on the login flow, then contact support if access issues persist.
Account structure supports controlled access patterns. For stricter governance, coordinate role and account ownership workflows internally.
Contact support with your request details. Requests are processed subject to verification and applicable legal obligations.
Email [email protected] and include your account context, page/feature involved, and expected outcome so the team can respond quickly.
Use strong credentials, controlled account ownership, and documented onboarding/offboarding procedures so access remains traceable and limited.
Share account context, affected page or feature, timestamps, expected outcome, and screenshots. This reduces back-and-forth and speeds resolution.
Requests are processed after identity/account verification and according to legal obligations and platform data handling policies.
Still need help? Reach out at [email protected] and include screenshots or URLs for faster troubleshooting.