Intelligent Technical Solutions, a managed IT services provider operating in 12 US cities. This audit covers technical SEO, content quality, schema, performance, AI search readiness, local SEO, and search experience.
Real-user CrUX performance is fast. Schema is stronger than initial scan suggested: every city page carries full LocalBusiness with GBP @id, AggregateRating, OpeningHours, and sameAs to LinkedIn + YouTube. The biggest remaining opportunities are homepage content depth and AI-citability.
Ranking in AI Overviews, Perplexity, ChatGPT, and Bing Copilot relies on three things: clean technical access, citation-ready content, entity trust signals (LinkedIn, YouTube, structured data). ITS clears the entity trust layer (LinkedIn + YouTube in schema). Held back by content depth and llms.txt redirect.
The site has two stories. Real users on real devices (CrUX field data) get a fast experience. Google's Lighthouse mobile throttling exposes a YouTube embed problem that punishes prospects on slower devices and any new traffic before CrUX kicks in.
| Performance | 65 / 100 |
| LCP | 4.8s |
| TBT | 330 ms |
| CLS | 0.043 |
| Performance | 42 / 100 |
| LCP | 26.7s |
| TBT | 500 ms |
| CLS | 0.0 |
| LCP p75 | 1,806 ms |
| INP p75 | 59 ms |
| CLS p75 | 0.003 |
| Verdict | FAST |
An earlier version of this audit listed four critical issues built around broken URLs (/managed-it-services, /contact, /cybersecurity) and a Sacramento NAP conflict. On verification, those URLs are not pages that exist or are linked anywhere on the site; they were tested speculatively, and a 404 on a URL nothing references is normal, not a defect. /cybersecurity in fact returns a live page, and the Sacramento details could not be confirmed against the crawl data. All four have been removed. The sections below reflect observed page content and the June 1 conversion pass; any remaining third-party specifics (directory listings, review counts) should be confirmed before action while a full re-verification is completed.
These are one-to-three-day workstreams. Stacked together they move the overall score from 64 into the 80s.
Each of the eight service cards on the homepage (Cybersecurity, Managed IT, Co-Managed IT, Cloud, Compliance, VoIP, Analytics, AI) is a 13 to 18 word fragment. AI Overviews, Perplexity, and ChatGPT need 130 to 160 word self-contained answer blocks to extract a citation. The Phoenix managed-IT-cost blog post already demonstrates the right structure: question H1, question H2s, specific numeric data, named CEO quote. Apply that pattern to the homepage.
No Google Maps iframe, no GBP profile link, no reviews widget, no "Get Directions" link on any city page. This is the visual equivalent of the schema gap above: Google has no on-page evidence that this URL is the canonical web representation of the GBP listing. Adding even a static Maps embed with the GBP place_id resolves the connection.
ITS has 700+ clients and 8-to-10-year average client relationships, yet shows zero reviews on Clutch, the #1 MSP buyer discovery platform. Competitors with 20+ reviews rank above ITS in every Clutch category and benefit from Clutch's domain authority. A 5-email drip to existing clients with a direct Clutch review link would realistically produce 20 to 40 reviews in 60 days. This single action moves ITS from invisible to category-ranked.
The BBB Las Vegas listing shows a different address (2880 Meade Ave Suite 350) and a different phone number ((702) 869-3636) than the website (3330 W Desert Inn Suite B / (702) 605-6670). This is a confirmed two-field NAP conflict on a Tier 1 directory. Google's local algorithm treats this kind of citation disagreement as a trust penalty.
Two basic browser security headers are not present in the HTTP response. Without X-Frame-Options, the site can be embedded in an iframe on any domain (clickjacking). Without X-Content-Type-Options, browsers may MIME-sniff and execute files differently than declared. The Permissions-Policy header is present but malformed (value is the string "true", which is not a valid directive). All three are added or fixed in two minutes via a Cloudflare Transform Rule with no HubSpot changes required.
The robots.txt has rules for the wildcard user-agent and a few HubSpot internals, but no named rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, CCBot, Applebot-Extended, or Diffbot. They all inherit the wildcard rule (allow), but no positive opt-in signal tells AI search platforms ITS welcomes indexing. The sitemap URL also uses http:// instead of https://, which some crawlers will not follow.
The Chicago city page mobile lab LCP is 26.7 seconds. The homepage mobile lab LCP is 4.8 seconds. The 22-second difference is entirely caused by three YouTube embeds on the city page eager-loading 9.5 MB of player JavaScript. Real users with CrUX-quality connections do not see this delay, but anyone on a slower device or first-visit-uncached condition does. This is the single highest-impact performance fix on the site.
Each of these is a meaningful improvement on its own. Stacked together they sharpen content and entity signals enough to compete in AI Overviews.
"Transform IT Challenges into Business Advantages" and "Unlock Your Technology's Full Revenue-Driving Potential" don't match how prospects search or how LLMs extract answers. The Phoenix managed-IT-cost blog post correctly uses question H2s ("What's the total cost?", "What are the factors?") and is the strongest AI-citable page on the site. Apply that pattern sitewide.
"Federal-grade cybersecurity services to protect your networks" is 11 words. AI systems need 130-160 word self-contained answer blocks to extract a citation. Every service card on the homepage is currently uncitable. The fix is content expansion, not template restructuring. HubSpot will render longer blocks without complaint.
jQuery 3.6.0 loads synchronously from cdnjs (no async/defer). CallRail swap.js, HubSpot i18n bundle, production JS bundle, and Hero JS all load synchronously in head. Every sync script blocks rendering until it downloads and executes. jQuery alone is ~90KB minified. This is the primary LCP risk outside the YouTube embed issue.
The HubSpot conversations widget loads 565 KB of assets on every page visit and consumes 238 ms in a single long task. Google Tag Manager (plus GA4, LinkedIn Insight, Bing UET, Ads remarketing) adds another 464 KB. Both should defer until user interaction.
The Detroit page address is 100 W Big Beaver Rd, Troy, MI (15 miles north of downtown Detroit). The Los Angeles page address is 489 E Colorado Blvd, Pasadena, CA (12 miles east of downtown LA), with a (626) area code. Both create proximity penalties for the metro the page is targeting. Map pack rankings are weighted on proximity, area code, and address city alignment.
The Oakland location page lists a (415) phone number, which is San Francisco's area code. Directory scrapers will flag this and may auto-correct to SF, breaking the Oakland citation chain.
None of these will move the score materially. They're included so the team can pick them up while waiting on larger fixes to deploy.
Worth saying out loud: ITS has a solid technical foundation. Real-user performance is fast, the site is fully crawlable without JavaScript, and the asset that matters most for AI citation (the Phoenix cost blog post) already exists.
This is the order we'd execute if we were running the program. Critical first, then High, then content depth and entity expansion.
The May 31 audit read itsasap.com through a pure SEO and AI-readiness lens. On June 1 we re-ran the homepage through three skills we just added to the stack: conversion psychology (CRO), AI-citability content (AEO/GEO), and Reddit demand research. Everything below is additive. The 64/100 technical score is unchanged; these are revenue and visibility levers the SEO pass structurally could not see.
Before (May 31): eight SEO categories covering crawlability, schema, performance, GEO, local, and search experience. Strong technical bones. After (June 1): six new findings the SEO pass could not produce, because conversion friction, on-page trust psychology, content freshness, and community demand sit outside a technical crawl. Two of them (the broken trust counters and the freshness gap) are quick homepage fixes with outsized impact.
The hero stat band shows "Confident Clients," "Devices Protected," and "Years Serving Clients" with the numbers obscured or displaying as "$0" and "0+". A social-proof counter that reads zero is worse than no counter at all: it actively signals a brand-new or failing vendor, the exact opposite of the truth. ITS has 700+ clients and 8-to-10-year average relationships. The strongest trust asset on the page is currently anti-converting.
ITS holds MSP 501, MSSP Top 250, and a 98% client-satisfaction rate, but the homepage surfaces none of them above the fold. Awards and third-party recognition trigger authority bias, the single fastest trust shortcut for a high-consideration B2B purchase. Right now they live behind a "Trust Center" link that most prospects never click, so the proof is real but invisible at the moment of decision.
"Schedule a Meeting" is the primary call to action everywhere, which is a high-commitment ask for a first-time visitor still comparing vendors. The "Managed IT Pricing in 1 Minute" estimator is the ideal low-commitment first step (foot-in-the-door), but it sits secondary. There is also no SLA or uptime guarantee stated anywhere, so a buyer weighing the switch has nothing to offset the perceived risk of regret.
No page carries a visible publish date, "last updated" stamp, or modified-time metadata. AI engines weight recency heavily: content updated within three months averages 6 citations versus 3.9 for content over two years old (SE Ranking, 2025, 2.3M pages), and AI assistants cite content 25.7% fresher than traditional organic results (Ahrefs, 2025, 17M citations). ITS publishes regularly but throws away the freshness signal by never dating anything.
The seven named case studies say things like "fixed the issue" with no quantified outcome. The two highest-impact GEO levers are adding statistics (+33% AI visibility) and adding authoritative quotations (+41%), per the GEO study (Aggarwal et al., KDD 2024). A testimonial that reads "cut our downtime 87% and saved $40K a year" is extractable and citable; "great service" is not. The Phoenix cost blog already proves ITS can write in this register.
The buyers ITS wants are asking two questions in r/sysadmin, r/msp, r/ITManagers, and r/smallbusiness. First: "how much should managed IT cost?" (the market answer is $75 to $250 per user per month, with hidden costs adding 30 to 50%). ITS already ranks-ready on this with the Phoenix cost blog, but it is one post, not a hub. Second: "how do I know my MSP is failing / when do I switch?" (slow tickets, surprise bills, no proactive support, missed SLAs). ITS has no content here, and these are the highest-intent switchers in the market.
We rebuild MSP-grade local SEO and AI visibility programs from scratch. Schema, GBP, content, performance, the whole stack.
Email info@myseodesk.com Call (434) 236-9027