Notes for the Pro Link Solutions SEO team

Prepared for Pro Link Solutions — Brandon Rangel / IgnitivIO Date: August 28, 2026 · Scope: prolink.solutions site review

First, what's already working

I want to lead with this because it's genuine and worth naming:

The technical foundation is clean. HTTPS with HSTS preload, valid sitemap.xml with 37 URLs and correct content-type, canonical tags across every page checked, proper mobile viewport, and a robots.txt that actually includes the sitemap directive. That's a real baseline — plenty of Duda sites don't get this right.
NAP is consistent across the site — same phone, same Lubbock TX presence, same brand handling from page to page.
Geo coverage is well-executed. Six Texas metro landing pages (Lubbock, Austin, Dallas, Houston, San Antonio, Amarillo) plus locally-titled blog posts targeting the same cities. That's the right structure.
Homepage has JSON-LD. WebSite and GeneralContractor blocks are present and well-formed with correct address and Place data. Not every commercial site does this either.
Home page title, meta description, and H1 are all in place across the pages I sampled (/, /about, /common-questions, /landscaping-and-irrigation, /service-area/lubbock-tx).

That's the "credit where credit is due" section. Everything below is meant as ammunition for the roadmap, not a critique of what's been shipped.

Findings worth prioritizing

I've narrowed this to the items that are (a) genuinely broken, (b) likely to move a metric, or (c) blind spots that are hard to catch from inside the account. I've cut anything that's routine hygiene you'd already have on the plan.

1. `/contact` page is missing its `<title>` tag and `<h1>` (verified via curl)

Contact is the highest-intent page on the whole site — where quote requests get initiated — and it currently has nothing for Google (or an AI answer engine) to display or cite. Adding both would give the page a real chance to rank for branded searches like "pro link solutions contact" and would fix the SERP snippet for anyone Googling the company by name.

Suggested fix (Duda-native): Contact page → SEO tab → set Title to "Contact Pro Link Solutions | Commercial Property Maintenance in TX & the South". Add an H1 element at the top of the page: "Request a Property Maintenance Proposal."

2. No JSON-LD schema on any of the 10 service pages or 6 service-area pages

The service pages (roofing, HVAC, plumbing, landscaping, parking-lot services, concrete, glass, garage doors, painting, sheetrock/drywall, snow & ice) and the service-area pages are the ones meant to rank for queries like "commercial roofer Lubbock" or "commercial HVAC Dallas." Right now they have no structured entity for Google to attach a Service + LocalBusiness relationship to.

Expected outcome of adding it: Google Local Pack visibility on those queries becomes consistent instead of sporadic, and the pages become eligible for richer SERP treatment. Duda supports custom HTML blocks in page settings — one Service + LocalBusiness template can be adapted per page in ~10 minutes each. Happy to share the template.

3. `/common-questions` FAQPage schema contains only 1 Question, though the page renders many

Users see the full FAQ, Google only sees one entity. Expanding the schema to match the visible content (8–12 Q&As covering pricing, response times, service areas, insurance, emergency service) unlocks FAQ rich-result eligibility and gives AI answer engines something concrete to cite when they respond to related questions.

Duda-native fix: their FAQ widget auto-generates full FAQPage schema — swapping the current custom implementation for the widget is usually the fastest path.

4. Homepage schema `@type` is `GeneralContractor`; `LocalBusiness` + `ProfessionalService` would be a stronger signal

For a multi-trade facilities maintenance company serving retail, restaurants, healthcare, and financial properties, ["LocalBusiness", "ProfessionalService"] is a more accurate — and more Google-friendly — declaration than GeneralContractor. Keep the existing address, phone, and Place blocks; only the @type needs changing.

5. AggregateRating is missing from LocalBusiness schema

If Pro Link has 5+ real Google reviews on the GBP, adding an aggregateRating node to the homepage schema is the single biggest trust-signal upgrade available — it enables star-rating rendering in SERPs. If review count is still low, this is a "queue for later" item.

6. Hero image is a 2.7 MB PNG (`db8cc995-...-1920w.png`), preloaded

This is a performance issue rather than an SEO-tag issue, but it flows through to Core Web Vitals (LCP specifically) and Google's page-experience signals. Re-exporting the hero as a WebP at 150–250 KB, or a JPG at 85% quality, would cut LCP by an estimated 2–4 seconds on mobile. Duda auto-serves WebP if a smaller source is uploaded.

7. Service-area pages have no `areaServed` markup

Small addition; noticeable local-search impact. Each service-area page (e.g. /service-area/lubbock-tx) would benefit from a LocalBusiness schema block scoped to that city with an areaServed field naming the surrounding metros served from that location.

Three items outside SEO scope — surfacing for the business, not for your queue

These are ops/brand items rather than search-optimization work. Flagging them for Jacob's side of the house so they don't sit in the SEO backlog by mistake:

The phone number (806) 993-9391 is shared with lubbockproservices.com (the residential/local brand under the same LLC, also on Duda). Both sites route inbound calls to the same line. This is a brand-experience and call-routing question — probably intentional today, but worth an explicit decision about whether the two brands should have separate numbers as Pro Link's national commercial pipeline scales.
Google Business Profile linkage isn't clearly verifiable from the outside. Worth confirming the GBP is claimed, is linked to prolink.solutions (not the lubbockproservices.com domain), and carries the correct category (Property Maintenance / Commercial Contractor rather than a residential category).
Reputation-platform presence — no Birdeye/Podium-managed review widget was found on the site. If review-collection is running through another tool, no change needed. If it's not running, that's a business decision worth surfacing.

Suggested sequencing (only if useful)

Week 1: items 1 and 4 (small edits, high visibility) + start the service-page schema rollout (item 2).
Weeks 2–3: finish item 2, expand item 3, ship items 5–7.
Ongoing: re-check the three business-side items above with Jacob's team.

Happy to walk through any of this — no pressure on adopting all of it, and I know you'll have context on what's already been tried or discussed internally.

— Brandon Rangel · IgnitivIO · [email protected] · ignitiv.io