I started SEOlutions.com to document my journey learning search engine optimization while working on my own websites.
I’m a wireless consultant, not someone who started with formal SEO training. I use ChatGPT, Claude, and Gemini to help research, improve, review, and learn from my websites.
But on November 21, 2026, we discovered something we should have done from the beginning: We should have built a WordPress SEO site inventory before asking AI to optimize anything. Discovering that mistake took hours.
The Google Analytics Problem That Exposed Our Workflow
During our review of SEOlutions.com, Google Site Kit reported an error and showed zero visitors.
But the actual SEOlutions.com Google Analytics property showed 54 active users and 57 sessions over the previous seven days.
Site Kit’s zero didn’t mean the site had no visitors. Site Kit was connected to the Google Analytics property for another one of my websites.
We selected the correct property, and the error disappeared. We still need to confirm that the refreshed Site Kit dashboard reports display correctly.
This was a measurement-setup correction. It did not demonstrate an increase in Google rankings or website traffic.
Hours Spent Documenting What We Should Have Known
I spent several hours working with ChatGPT, sending screenshots, recording WordPress videos, checking settings, and correcting information that should already have been available. The later portion of our documented work alone covered approximately an hour and forty minutes. That is only part of the work, not an exact timesheet.
We wanted a reliable technical reference that ChatGPT, Claude, and Gemini could all use. We documented:
- The Sinatra WordPress theme, colors, typography, and layout settings.
- Installed plugins, including active, inactive, and must-use plugins.
- Custom CSS and WPCode modifications.
- Eight categories and 36 tags.
- Yoast indexing, archive, and sitemap settings.
- Permalinks and existing redirect rules.
- Google Search Console and Google Analytics connections.
- Contact form settings and successful email delivery.
- Hosting backup coverage and outstanding exceptions.
Some Customizer values were captured while an unpublished draft was pending. Seeing a setting in the editor does not automatically mean it is live on the website.
What Went Wrong Along the Way
Several problems had nothing to do with Google’s ranking algorithms.
- ChatGPT asked for plugin information already visible in recordings I’d provided.
- We spent unnecessary time revising a social-sharing image because its intended preview size wasn’t considered first.
- During backup troubleshooting, an unfamiliar icon was incorrectly identified as a report button. It actually opened restoration options. We stopped without restoring anything.
- I deleted Backuply before confirming whether my hosting backup covered SEOlutions.com specifically. We later confirmed that it did, but the Xcitium file backup showed Completed with Exceptions, and another screen reported Last backup failed. A full restore has not been tested.
These were workflow problems. They consumed time I could have spent improving my other websites.
The Website Inventory Every AI Should Have
Going forward, every website should have a short, verified configuration reference before major SEO changes.
| Priority | Area | What to document |
|---|---|---|
| 1 | Backups | Site-specific coverage, latest clean backup, and recovery readiness |
| 2 | Analytics | Correct GA4 and Google Search Console properties |
| 3 | Lead generation | Contact forms and verified notification delivery |
| 4 | Indexing | Yoast settings, sitemaps, categories, and tags |
| 5 | Website structure | Permalinks, important redirects, and navigation |
| 6 | Technical setup | Theme, plugins, caching, CSS, and code snippets |
| 7 | Design | Fonts, colors, layouts, and image requirements |
| 8 | Content | Existing posts, target topics, internal links, and author information |
Verify what already exists before recommending something new. An AI suggestion can be unnecessary or harmful when it doesn’t account for a website’s existing plugins, settings, or code.
How ChatGPT, Claude, and Gemini Will Collaborate
We now have one shared Google Doc with separate tabs for my websites and a research and change log preserving the detailed history.
- ChatGPT: Organize the work, maintain site inventories, develop content, and coordinate approved changes.
- Claude: Challenge technical recommendations, review SEO strategy, and identify inconsistencies.
- Gemini: Review available Google-related evidence, Analytics, Search Console, and technical claims.
Each AI should record its own findings and corrections in the shared document. That gives the team one reference instead of three assistants working from different assumptions.
We’ve also established a publishing rule: when an article is ready for WordPress, every metadata field needs its own copy button, and the complete HTML must be copyable in one action. A downloaded file alone is not enough.
Will This Improve Our SEO?
We haven’t proved that yet.
We corrected an Analytics connection, verified that our contact form delivers messages, documented the site’s configuration, and identified an unresolved backup issue. Those are meaningful operational improvements, but they don’t establish higher rankings or more organic visitors.
We’ll apply this inventory-first process to WirelessConsultant.net and MobileWiseguy.com and see whether it reduces duplicated work, mistakes, and wasted time.
The Lesson From SEOlutions.com
A website documenting SEO experiments should have had its own technical baseline at the beginning. We skipped that step.
Now SEOlutions.com’s baseline is documented, our three-AI collaboration has a shared reference, and we have a repeatable starting point for the other websites.
The goal isn’t for AI to generate more recommendations. The goal is for three AIs to work from the same verified information, make fewer mistakes, and produce improvements we can actually measure.
For more real-world experiments, explore our SEO case studies and How Long Do SEO Changes Take?