Chris - Local SEO

Every entity on a roofing page is a node Google already has. Here's the bot finding all 40 of them. Entities are just nouns. The nouns that come up when you talk about the service: roofer, roof shingle, flashing, ridge vent, ice dam, home insurance. Google doesn't only count your keyword, it measures these too. Each one has a Wikipedia page, a Wikidata item and a Google Knowledge Graph ID. I put all three in knowsAbout, one Thing per entity, and the page inherits everything Google already knows about roofing without stuffing it on the page.

Six placements on DR 80+ sites from one press release. A recent release I sent landed on: AP News, DR 92 USA Today, DR 92 Business Insider, DR 92 NewsBreak, DR 83 Barchart, DR 81 Manila Times, DR 80 One piece of writing. Each of those is a page about the business with its links in the body, on a domain that has thousands of backlinks of its own. That's one press release package. DMs open.

My Press Releases are syndicated. One release is distributed to the publications. Yahoo Finance, Business Insider, USA Today, about 500 more. Each one prints its own copy. The links are already in the body, so every copy carries them. One piece of writing. 500 to 550 referring domains. Sometimes around 750. Not one article. One article, printed hundreds of times, each on its own domain, each pointing at your site. That's what syndicated means.

Want to know if Google is actually visiting your site? Search Console tells you, for free, in about two minutes. Open Google Search Console. If it isn't set up, most hosts and website builders have a one, two or three click process for it, or you change one DNS record. Left side, scroll all the way down. Settings. Crawl stats. Open the report. Read three things: how many times Google came by, the server responses it got, and what type of Googlebot is hitting your site.

Here's every entity you want on a roofing page, and how to wire each one to what Google already knows. Entities are just nouns. The nouns that come up when you talk about the service. Google doesn't only count your keyword, it measures these too. The roofing list: Roofer, roof, roof shingle, asphalt shingle, metal roof, roof tiles, slate, flat roof, gable roof, hip roof, roof pitch, flashing, rain gutter, downspout, soffit, fascia, eaves, dormer, skylight, chimney, ridge vent, attic, rafter, truss, tar paper, bituminous waterproofing, EPDM rubber, TPO, hail, ice dam, wind, storm, leak, water damage, mold, home insurance, warranty, building insulation, ventilation, nail. Why these: Google already has a knowledge graph entry for every one of them, and it boils what's on your page down to a math equation. You don't have to teach it what a ridge vent is. Words are fuzzy. The ID pins it. How to wire one, in your schema: Find the Wikipedia page. en.wikipedia.org/wiki/Ridge_… Find the Wikidata item. Every Wikipedia page has one. wikidata.org/wiki/Q7332722 On that Wikidata page, find the Google Knowledge Graph ID. It's listed as the Freebase ID: /m/0g4dt1 Link the ID as a Google search URL, not the bare ID and not a page on your site: google.com/search?kgmid=/m/0… Put all three in knowsAbout. One Thing per entity, a two or three sentence description in your own words, then the three URLs in sameAs. The same Thing goes in about or mentions on the page, and every city you serve gets the same treatment in areaServed. Node after node telling Google you're the expert. You inherit everything it already knows about roofing without stuffing it on the page. Do the whole list above. Then do it for every city you serve.

Wow, 44% of pages ranking in the 1-3 position were cited in the A.I overview. Ranking well in Organic helps a lot, but does not guarantee a citation. I'm currently still scrapping Google A.I Overviews. I'm getting some fantastic data that I'll continue to share as I learn more.

Someone just purchased our $2,000 Press Package and asked for a pictograph. So they can show their webguys as to what a Press Release strategy is. Here's the video. Here's what's included: 5 10 Top UK & US Publications Up to 3,750 Backlinks + 5–10 DA 90+ Editorial Backlinks Targeted Journalist Pitching (175k+ database) Google News Inclusion Newsroom Inclusion Editorial Transformation Associated Press Distribution Google News Inclusion Newsroom Inclusion Associated Press Business Insider Digital Journal Benzinga NewsBreak Barchart GlobeNewswire MarketWatch USA Today Yahoo Finance

I'm currently scrapping Google A.I overviews. This will give me first source data on where Google is pulling from and why. Man I love reverse engineering things.

Right click your website. View source. If you can't scroll for a while, Google can't read it. That's the 30-second check. On a static HTML site you'll scroll through every word on the page as raw code. On a site built by one of the AI website builders you'll see almost nothing: a script, and the script tells the visitor's phone to go build the page. Here's why that costs you: Google's crawler grabs the raw code. Most of the time it does not have rendering turned on, so it sees the script, not your content. All the on-page work you did isn't there. The page goes into a secondary queue to be rendered later. Best case about three days. It can be weeks or months. Every edit you make waits that long to be seen. It isn't only the full-JavaScript sites. A WordPress plugin that pulls your Google reviews in with JavaScript hides that part too. Google sees maybe 80% of the page. The other 20% of your optimization is gone. The AI tools are worse. In a test with three pages, one fully built by JavaScript, one with a plain header and footer but JavaScript content, and one heavy graphics site, ChatGPT, Claude and Perplexity failed all three. They saw the menu, the footer and the cookie text. Gemini and Copilot passed the first two because they lean on Google's and Bing's indexes. The same script slows the page. Nine seconds to load on a 3G connection, and the person out looking for your service doesn't wait. The fix: pure HTML, or server-side rendering turned on so the server hands over the finished page. Then every crawler, every search engine, every AI that visits sees it the first time, every time. I build every client site static. Never a hundred percent JavaScript.