The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
I developed Square Accounting's content-led growth system across positioning, SEO research, editorial strategy, website messaging, landing pages, LinkedIn, email, repurposing, and analytics.
The work connected high-intent tax topics to relevant service offers and conversion paths for Florida business owners, real estate investors, and high-income professionals.
Verified outcomes included organic traffic growth, stronger keyword visibility, improved website conversion, and more qualified inquiries. Exact analytics are redacted for confidentiality.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Designed a clean, modern, and responsive business website concept to showcase services, build trust, and help businesses attract potential customers.
Not only is the design clean, but you also did a great job making sure it works well across different devices with a responsive design.
Check the Live Sitemap Before Signing Off the Release
A sitemap can export correctly while the live website still serves an older URL list. The task needs a check at the public sitemap address after deployment.
That check should compare the published file with the pages the team agreed to include.
Imagine an export containing 200 URLs. The public sitemap also contains 200, but it still lists a retired service page and omits the new replacement. The totals match. The contents do not.
Before closing the task, check:
• The production sitemap address returns the expected XML.
• Its complete URL list matches the agreed inventory.
• Each intended page type is represented, including a newly published page.
• Deliberately excluded pages remain absent.
• Someone owns the process that keeps the file current.
Start with the sitemap already on the site. It may be an index pointing to several smaller files. Include those files in the comparison so a working index does not hide an outdated section underneath it.
Keep the inventory decision explicit: which service pages, locations, articles or products belong in this release? A crawler's export tells you what it discovered. Compare that list with the pages the site was supposed to publish.
Open a sample of the listed URLs as well. Check that they reach the intended production pages and use the preferred addresses. If the sitemap includes modification dates, those dates should reflect significant page updates; exporting the file again does not make every page newly updated.
For a site that publishes regularly, document how new pages enter the sitemap and how retired pages leave it. An automated generator still needs clear inclusion rules and a check when those rules change.
Keep the public address, inventory comparison and update owner in the release notes. Make the sitemap discoverable through Search Console or robots.txt, and check for retrieval or processing errors. Submission does not guarantee that every listed page will be crawled or indexed.
I put together the generation, export and publishing steps in the full guide on Technical SEO Notes:
https://technicalseonotes.org/how-to-generate-and-export-an-xml-sitemap/
Projects and client work: NikoCodes
https://nikocodes.com/
Solid checklist. I'd add lastmod: if every release stamps today's date on every URL, Google learns to ignore it. It should only change when the page content changes. Also worth confirming every sitemap URL returns a direct 200, not a redirect.
Are AI Search Engines & LLMs Diluting Your GSC Traffic Data? 🤖📉
If you’re seeing sudden spikes in impressions with 0 clicks in Google Search Console, you're not alone.
When LLMs like ChatGPT, Perplexity, Claude, and Gemini process user requests, their web-browsing agents run background searches (fan-out queries) using direct site: operators to find and verify official sources.
Want to isolate this AI-driven query data in your own accounts?
Run this custom Regex filter under Performance > Query > Custom (regex) in GSC:
site:|\b(chatgpt|perplexity|claude|copilot|gemini|searchgpt)\b
(Make sure to select "Matches regex" in the dropdown)
What this highlights:
• High-impression, zero-click fan-out searches generated by AI web-browsing bots
• Brand searches where users explicitly look for AI summaries or integrations • Clearer CTR data by identifying AI search noise from standard organic traffic
Have you checked for AI query footprints across your client sites yet?
What patterns are you seeing?
Drop your findings below! 👇
#SEO #SearchEngineOptimization #GoogleSearchConsole #GenerativeAI #AEO #TechnicalSEO #AISEO
Useful regex. Before blaming AI agents for every spike, it's worth checking the opposite effect: when Google stopped supporting the num=100 results parameter in September 2025, many sites saw desktop impressions drop overnight because rank-tracker scrapes stopped counting....