Getting started with PixelGR dashboard and your first site scan
Step-by-step guide to launching your first site scan from the PixelGR dashboard, understanding the AI visibility score, and publishing fixes into WordPress.
To start, sign in to PixelGR, add the site you want to analyze, and click the Scan button to run your first site scan. The scan returns an AI visibility score and a prioritized list of fixes you can review and publish directly into the WordPress editor.
Running your first site scan in PixelGR
Run your first site scan by adding your site to PixelGR, verifying ownership, and clicking Scan from the dashboard.
Open PixelGR, choose Add Site, and enter the site URL and basic contact details. Verification options include placing a verification file, adding a meta tag, or connecting with your hosting provider. Once verified, pick the scan scope: full site or a targeted subfolder. For most small and mid-size sites a full site scan is the right place to start. After you start the scan you can leave the dashboard; the scan runs and returns results in the Scans list.
What to expect during the first run
- Progress updates appear in the scans table while pages are crawled and analyzed.
- When complete you will see an AI visibility score, a list of issues by priority, and suggested fixes grouped by type.
- You can export results, export a PDF report, or begin implementing fixes directly from the dashboard into WordPress.
What does a PixelGR site scan check for?
The PixelGR site scan checks technical SEO, page performance, structured data, content quality, accessibility signals, and local listings related to MapsGR.ai and LocalGR.ai synchronization.
Specifically the scan inspects crawlability and indexability, looks for duplicate content and meta problems, runs performance checks that map to PageSpeed Insights categories, validates schema and JSON-LD, and flags local listing mismatches. Performance checks use the same category model that PageSpeed Insights and Lighthouse report, which includes performance and SEO among other categories as documented by the PageSpeed Insights API categories reference: PageSpeed Insights API categories.
The scan also reports basic accessibility flags that correlate with accepted WCAG guidance and highlights areas where structured data could improve discovery in local search results.
What is the AI visibility score and what does it measure?
The AI visibility score is a single composite metric that reflects how discoverable your site is across organic and local search channels based on PixelGR’s combined checks.
The score aggregates technical SEO health, structured data coverage, page performance, accessibility signals, and local listings completeness into an easy-to-read number and breakdown. For very large sites you should pay attention to crawl budget and how often you schedule scans, because Google defines crawl budget as the set of URLs that Google can and wants to crawl and that becomes relevant as a site grows: Google documents considerations for large sites and crawl budget management in their crawling guidance, including examples for larger sites of tens of thousands of pages and beyond: Google’s crawl budget guidance.
Interpreting scan findings and prioritizing fixes
Use the dashboard’s issue priority labels to choose fixes; start with high-impact technical and local listing fixes, then move to performance and structured data improvements.
High-priority items are typically issues that block crawling or indexing, incorrect local business data that confuses maps, and errors in structured data that prevent rich results. Medium priorities include performance opportunities and content optimizations. Low priorities are minor accessibility adjustments and cosmetic content suggestions. PixelGR groups fixes by page, template, and site-wide so you can apply a single change where it will fix many pages at once.
Publishing fixes from PixelGR into WordPress
You can publish fixes directly into the WordPress editor from PixelGR using the built-in WordPress integration.
From a reported issue click Edit in WordPress to open the WordPress editor for that page or template. PixelGR maps suggested changes into specific editor fields such as title tags, meta descriptions, and structured data blocks. Approve the change in the editor and use WordPress’s Publish or Update button to push the fix live. For schema changes PixelGR generates JSON-LD snippets that are added to the page head or to a schema block in the editor.
How does PixelGR handle structured data and schema to improve discovery?
PixelGR creates and validates structured data, recommends schema for business, product, service and local listings, and lets you publish JSON-LD directly to your site or templates.
The dashboard validates structured data and highlights missing types and required properties. PixelGR suggests schema based on page type and business category, and can add businessName, address, openingHours, geo coordinates, and contactPoint fields where appropriate. When you publish from the WordPress editor the schema is added as JSON-LD so search engines and map services can read it more reliably.
What local SEO and maps-related products does PixelGR integrate with?
PixelGR integrates with MapsGR.ai and LocalGR.ai to synchronize local listings and improve map visibility for businesses in West Michigan and beyond.
MapsGR.ai focuses on map presence and citation health, while LocalGR.ai helps manage business listings across directories. PixelGR coordinates structured data updates on your site with listings updates so your contact details and hours are consistent across the web. This combined approach reduces data drift between your site and local listings and improves the chance that knowledge panels and local packs show correct information.
What should I know about performance testing and accessibility checks?
PixelGR reports performance using the same underlying metrics that PageSpeed Insights and Lighthouse use, and the dashboard surfaces accessibility issues aligned with current WCAG guidance.
PageSpeed Insights has evolved with Lighthouse and was updated to Lighthouse 12.0 on May 10, 2024, which changed some reporting behavior and categories as noted in the PageSpeed Insights release notes: PageSpeed Insights release notes. PixelGR maps its performance recommendations to those categories so you can take the same corrective actions you would in Lighthouse and PageSpeed reports. For accessibility, PixelGR flags issues that relate to WCAG criteria and highlights where your pages diverge from recommended success criteria; for reference, the W3C documents the new success criteria added in WCAG 2.2 as well as the baseline guidance in WCAG 2.0: W3C changes in WCAG 2.2 and W3C WCAG overview.
What about scan frequency, crawl budget, and large sites?
Schedule scans based on site size and content churn, and be mindful of crawl budget considerations for very large or rapidly changing sites.
If your site is very large or content changes daily you may need a tailored scan cadence and selective scanning to reduce redundant work. Google explains that for medium or larger sites with extensive pages and rapid content changes you should manage crawl capacity and demand carefully, and they provide guidance for large sites to troubleshoot crawl budget concerns: Google Crawl Stats report guidance for large sites.
Getting help and next steps
Get started by creating a PixelGR account, adding your site, and running your first site scan; PixelGR in Grand Rapids supports businesses across West Michigan with setup and ongoing support.
If you need help the dashboard includes inline help items, guided walkthroughs, and a support link to contact the PixelGR team. After your first scan, review the AI visibility score, apply the highest priority fixes in the WordPress editor, and schedule a follow-up scan to confirm improvements. When you are ready to expand, explore pricing & plans in the dashboard to add regular scanning, listings sync, and advanced reporting.
Running an initial scan is the fastest way to see where your site stands and to get actionable work you can publish immediately from PixelGR into WordPress. For businesses in and around Grand Rapids and West Michigan, PixelGR coordinates on-site fixes with LocalGR.ai and MapsGR.ai to help improve both organic and local discovery.
Frequently asked questions
How long does a PixelGR site scan take?
A PixelGR site scan completes in a single session but the exact time varies by site size and scope, and you will be notified in the dashboard when the scan finishes.
Can I publish fixes directly to my WordPress site from PixelGR?
Yes, PixelGR integrates with the WordPress editor so you can send suggested changes into specific editor fields and publish them from WordPress.
Do I need developer access to verify my site in PixelGR?
You may need access to add a verification meta tag, upload a verification file, or connect via your hosting provider, so administrator or developer access is typically required for verification.
Will PixelGR update my local listings automatically?
PixelGR coordinates with MapsGR.ai and LocalGR.ai to synchronize listing data, and you can enable automated listing updates in the dashboard as part of your plan.
Where can I find pricing and plans for regular scanning and listings sync?
Pricing & plans are listed in the PixelGR dashboard under the Billing or Plans section, where you can compare regular scanning, listings sync, and reporting tiers.
This article was written by ArticlesGR.ai, PixelGR's weekly article service. Want one like it for your business every week? Talk to PixelGR.
Sources
- Crawl Budget Management | Google Crawling Infrastructure | Crawling infrastructure | Google for Developers developers.google.com
- Crawl Stats report - Search Console Help support.google.com
- Release Notes | PageSpeed Insights | Google for Developers developers.google.com
- Categories (PageSpeed Insights API v5 (Rev. 19) 1.25.0) developers.google.com
- What's New in WCAG 2.2 | Web Accessibility Initiative (WAI) | W3C w3.org
- WCAG 2 Overview | Web Accessibility Initiative (WAI) | W3C w3.org