Indexing & crawl management
Page-indexing states, crawl budget, URL Inspection, sitemap reporting, non-indexed pages, and cleanup of low-value URLs.
39.5%
Best tweets about Technical SEO
43 Best Tweets About Technical SEO (2026)
Find the best tweets about technical SEO, including crawling, indexing, rendering, canonicals, site architecture, Core Web Vitals, and diagnostics.
Technical SEO audits, crawling, indexing, rendering, canonicals, architecture, performance, structured data, diagnostics, and measured fixes.
- Creators
- 31
- Updated
Original Xholic analysis
What 43 top Technical SEO posts reveal
The evidence set focuses on technical SEO diagnostics for crawling, rendering, indexing, sitemaps, URLs, and internal links. Posts frequently recommend validating crawler-visible output and using GSC, crawls, and URL-level data to investigate issues. JavaScript implementation and the conditions for scaling page inventories are recurring areas of disagreement.
- Dominant tone
- Positive
- Median score
- 17.0
- Leading format
- Case Study
- Recent posts
- 23.3%
44.2% of posts
All-time engagement
34.9% of posts
Published in 90 days
Conversation map
The themes creators return to
Crawling & rendering
Googlebot fetching limits, stateless rendering, JavaScript dependencies, server-side rendering, DOM verification, and crawler visibility.
27.9%
Metadata & structured data
Structured data, schema validation, HTML semantics, metadata, title handling, hreflang, and machine-readable page signals.
27.9%
Site architecture & internal linking
Information architecture, internal-link routing, topical hubs, service/location silos, and making priority pages discoverable.
23.3%
Technical auditing & diagnostics
Technical audit workflows using crawls, GSC, GA4, log data, segmentation, diagnostics, prioritization, and automated audit tooling.
23.3%
Performance & Core Web Vitals
Core Web Vitals, mobile performance, script and asset loading, font/image optimization, plugin impact, and Lighthouse diagnostics.
16.3%
URL & canonical control
Canonical tags, redirects, HTTP status handling, parameter URLs, duplicate signals, robots directives, and cross-domain sitemap problems.
11.6%
International technical SEO},{
International SEO implementation, including regional domains, XML sitemaps, hreflang, and cross-market URL signals.
7%
Tone and stance
Sentiment Positive leads
Author posture Supportive leads
Performance benchmark
- Median likes
- 51
- Median reposts
- 4
- Median replies
- 8
- Median views
- 5.7K
Posts with media make up 62.8% of this collection. Their median all-time score is 19.7, compared with 13.4 for text-only posts.
Format mix
- Case Study 34.9% Β· score 11.9
- Announcement 25.6% Β· score 15.7
- List 14% Β· score 21.7
- Opinion 11.6% Β· score 13.3
Consensus and debate
Where creators agree, and where they do not
Shared view
Use data and URL-level diagnostics in audits
Several posts describe a diagnostic workflow that combines site crawls, Search Console data, analytics or keyword data, indexing-state checks, URL-level actions, and sitemap reporting.
Shared view
Check crawler-visible content and critical signals
Posts emphasize checking what Googlebot fetches or receives in rendered output. They specifically call out keeping important HTML signals early in the document and investigating implementations that leave Google with little visible page content.
Shared view
Make priority pages easier to discover
Internal linking is presented as a way to improve page discovery and site structure. Suggested actions include fixing links to canonical URLs, strengthening contextual links, and ensuring content has clear link routes.
Open debate
How broadly should JavaScript be treated as a risk?
The posts differ in their framing of JavaScript. One argues that JavaScript rendering is broadly unreliable and favors server-side rendering, while Googlebot-focused posts describe defined fetch limits and implementation practices intended to keep critical content and signals accessible.
Open debate
How much technical work is worth prioritizing?
One post argues that many technical fixes will not affect traffic unless crawlability or indexing is impaired. Other posts advocate extensive audit checklists or highlight smaller fixes involving canonicals, internal links, low-quality pages, and indexable URLs.
Open debate
When is large-scale page expansion appropriate?
One post cautions against programmatic expansion when current pages are not consistently indexed or internally linked. Another promotes creating many local service-area pages with unique content and internal links, while a third flags risk in scaling programmatic pages across countries, languages, and YMYL categories.
What performs
Patterns behind standout posts
Top score outliers span diagnostics, rendering, and indexing
The five supplied score outliers cover Googlebot fetching and rendering, content-inventory auditing, JavaScript concerns, sitemap reporting, and a broad technical audit checklist. Their all-time scores range from 169.53 to 914.5, versus a dataset median of 17.037.
Announcements are a meaningful share of the set
Announcements account for 11 of 43 tweets (25.6%). The supplied examples cover Googlebot fetching behavior, a crawl API workflow, and agentic-commerce considerations.
Tutorials have the highest supplied format median score
Tutorials have the highest supplied format median all-time score at 44.977. The cited examples provide workflows for content inventories, individual sitemap submission, and international sitemap hygiene.
Statistical standouts
- View standout post 1 Score 914.5 Β· 53.68Γ median
- View standout post 2 Score 220.2 Β· 12.92Γ median
- View standout post 3 Score 194.9 Β· 11.44Γ median
- View standout post 4 Score 173.6 Β· 10.19Γ median
- View standout post 5 Score 169.5 Β· 9.95Γ median
Creator landscape
Who shapes this conversation
The five most represented creators account for 23.3% of the selected posts.
-
1. Aleyda Solis ποΈ
@aleyda
2 posts
-
2. Brodie Clark
@brodieseo
2 posts
-
3. Charles Floate π
@Charles_SEO
2 posts
-
4. Flavio Amiel
@fba
2 posts
-
5. Daniel Foley Carter
@foley_seo
2 posts
-
6. Glenn Gabe
@glenngabe
2 posts
Brodie Clark: sitemap reporting and international hygiene
Brodie Clarkβs posts focus on sitemap and indexing-report hygiene: submitting important child sitemaps individually, and checking sitemap, robots, and hreflang signals when regional domains are involved.
Jake Ward: audit and improve existing URLs
Jake Ward advocates reviewing existing URLs with crawl, ranking, and analytics data; assigning actions such as leave, merge, delete, update, or rewrite; and addressing smaller issues including cannibalization, internal links, and indexability.
Charles Floate: implementation constraints and content refreshes
Charles Floate posted about Googlebot fetch limits and the placement of critical HTML signals, and separately reported a case in which an established post gained visits after a targeted content refresh.
How this analysis was made
Themes, sentiment, stance, and post format are classified per tweet. All counts, shares, medians, creator concentration, freshness, and performance comparisons are then calculated directly from the published snapshot.
Xholic's all-time score compares engagement while accounting for reach, post age, and creator consistency. It is used for relative comparisons within this collection.
This report analyzes the exact 43-post snapshot shown below. AI identifies editorial categories and drafts explanations; all statistics are calculated from the snapshot, and every narrative claim is checked against cited posts before publication.
Best Technical SEO tweets
Top Technical SEO tweets from 31 creators
Ranked 01β43
- 01
@Charles_SEO Β·
The LEAD search engineer at Google just dropped a brand new blog post that confirms something most SEOs have never even heard of... Googlebot only fetches the first 2MB of your pages HTML = Everything after that cutoff doesn't exist to Google!!! Not fetched, not rendered, not indexed. And the Web Rendering Service is completely STATELESS - Meaning it clears local storage and session data between every request, so if your content depends on cookies or session state to render, Google can't see it. External CSS and JS files are fetched SEPARATELY with their own 2MB limit per file, and PDFs get a 64mb limit. So the structure and order of your code literally matters! And is why some CMSs are so much better out the box than others... Make sure you put your meta tags, title, canonicals, and structured data as HIGH as possible in the document. If they're below the 2MB cutoff, Google doesn't know they exist. Most OnPage SEO guides never take any of this into account, but most OnPage is surface-level. The real edge is understanding the infrastructure your content passes through before Google even evaluates it.
- 02
@jakezward Β·
Planning new SEO content for 2026? PLEASE do this first: 1. Get all your blog URLs into a spreadsheet. Use Screaming Frog to crawl and export. It provides other useful information like titles and descriptions. Connect further data sources: - Ahrefs - Google Analytics - Google Search Console 2. Enter each URL into Google Search Console or Ahrefs and find its best-ranking keywords. Add this data to the spreadsheet for each page: - Primary keyword (your main keyword) - Secondary keywords (variations and similar) - Current position for your target keyword(s) If a URL isn't ranking for anything? Find the most relevant keywords using Ahrefs. Then... 3. Audit each blog post and assign actions: - Leave: Content thatβs reached its full potential - Merge: Cannibalising or extremely similar content - Delete: Content that no longer offers value to users - Update: Small changes to improve the performance - Rewrite: Large changes to improve the performance 4. Spend a few weeks in Q1 implementing these actions to get more out of your existing assets. Prioritise updates and rewrites that have: - Target keywords in positions 4-20 - Higher conversion and $ potential - Easy improvement opportunities Remember: Not all of your Q1 content needs to be new. Look at your existing content first. You're likely sitting on many quick wins.
- 03
@jbobbink Β·
Google is gaslighting the entire SEO industry about JavaScript. I have the receipts. This week Google removed the "Design for accessibility" section from their official JavaScript SEO documentation. Their reason? JavaScript rendering is "no longer a barrier" for Google Search. I nearly choked on my coffee. I manage SEO across hundreds of properties. I see what actually happens when Google tries to render JavaScript sites. Every single day. This is the fifth update to the same document since December 2025, part of a systematic campaign to replace broad cautions with specific technical guidance Here is what I see that Google apparently does not. Content behind tabs, accordions, and "load more" buttons? Completely invisible. Google does not click. Google does not scroll. Google does not interact. That content simply does not exist for them. Structured data injected via JavaScript? Random. Google's own documentation on https://t.co/COodItApeI admits that JS-generated Product markup makes shopping crawls less frequent and less reliable. I see it break constantly. Images loaded through JavaScript? Good luck getting those indexed. Lazy-loaded images behind interaction events are a black hole. Internal links rendered via JavaScript? Onely proved Google needs 9x more time to crawl JS pages than plain HTML. Nine times. Their experiment showed 313 hours for JS versus 36 hours for HTML to reach the same depth. A 2024 counterpoint study by Vercel/MERJ found most pages rendered within minutes. And here is the part nobody is talking about. AI crawlers cannot render JavaScript at all. GPTBot, ClaudeBot, PerplexityBot. They see raw HTML only. Onely's 2025 research estimated about 70% of modern websites may be completely invisible to AI search because of JavaScript dependencies. So Google removes the warning. Developers lean harder into client-side rendering. And what happens? Sites become more dependent on Google's proprietary rendering pipeline while going completely dark for every competing search and AI system. Convenient timing. Google is not telling you JavaScript is fine because it is fine. Google is telling you JavaScript is fine because it benefits Google. Server-side rendering is not optional. It never was. Do not let a documentation update convince you otherwise. Sources: 1. Barry Schwartz, "Loading Content With JavaScript Does Not Make It Harder For Google Search" Mar 5, 2026 2. Google Developers, JavaScript SEO Basics (the removed section) 3. Google Developers, Structured Data with JavaScript (the shopping crawl admission) 4. Vercel "How Google handles JavaScript throughout the indexing process" Jul 20224
- 04
@brodieseo Β·
SEO Tip: don't just submit the sitemap index file in Google Search Console, you'll need to submit all important sitemaps individually also. When I get access to a client's GSC, often for very large sites, I unfortunately don't always have access to the indexing data that I need from the get-go. A core reason for this is when only the sitemap index file has been submitted, and not the individual sitemaps for core parts of a site e.g. products, categories, articles, guides etc. This approach effectively applies to all types of sites. Whether it be news publishers (where articles are often grouped within sitemaps by date), eCommerce sites, marketplaces, or sites of any kind. When you think about large sites that are maxing out on the number of pages that they're squishing into a sitemap (50K is the limit), you're losing a great deal of insight along the way, especially if you're only able to view page indexing for millions of URLs at a time. I actually think that Google should really do this automatically when sitemaps are detected within the index, due to the usefulness of the reporting, but I do also understand that it does require input from the site owner in the first instance. If you haven't added your sitemaps to GSC in this way yet, get it over and done with and make the change now. If you end up working with someone in a technical SEO engagement, they will be thankful that you did (if they understand the importance of this reporting view).
- 05
@foley_seo Β·
SEO is easy. SEO audit: β Tear down of Google Search Console Data β Build segments (non brand/brand) & sub folders (product/category/service/blog) β Last 3 month YoY comparison β Click gap analysis β Core update impact analysis & spam updates β Segment of decaying pages & queries β Crawl of website β Match decaying pages to word count, readability, internal links β Index performance analysis (dead, weak URLS etc) β GA4 data integration with decayed URLS / click gap β Integration of Bouce, Session, Engagement data β Divide word count by consumption time, identify unhelpful content β Set up another website crawl w/ GA4/GSC API & JS render β Export crawl, segment by priority β Render checks key pages (DOM analysis) β JS functionality review (CSR/SSR/Button Events/Dynamic Content) β Canonical checks (self ref, canonical child, non-value paths) Handling of dynamic/parameter URLS β Non value path handling (meta robots/robots) pagination, blog taxonomies etc. β JS Content/Links/Injection Events β HTTP header checks & handling (3xx/4xx/5xx) β HREFLANG β Internal link consistency (http 200 vs internal redirects) β GSC URL Inspection output dom (by page type) β Title & meta export with GSC CTR data - identify weak/gaps β Ensure all content accessible (sufficient link routes) β Rendering & peformance analysis (CWVs, INP, CLS etc) β Crawl stats review (type/bytes/freq) β Robots accessibility β Structured data / JSON / markup / validation β Content auditing NLP, quality, topical weight Niche compliance (YMYL) E-E-A-T & Integrity By performance & age (updated date/lastmod) By performance (word count/engagement time & WPM consumption) Query counts & query alignment (Relevance) Query dilution / topical dilution Cannibalising content Plagarism & Duplication checks Wayback update checks Fact-check validation Internal/external links Content query to anchor rel β Link auditing Ref domain accruement rate Segment by traffic performance Topical trust flow review Link context review Link distribution top pages Anchors PBN/Network checks OBL context Link consolidation & domain redirect checks Lost link checks Link spam reviews Disavow checks β Brand Trust Analysis Brand search volume Search sentiment Search variants Company details & consistency Trust signals (reviews, glassdor) Site policies UGC mentions β User behaviour Engagement analysis Heat, click, scroll map Custom explorations Bounce rates / eng time β Indexing Indexed vs non indexed page analysis Non index reason evaluation Clean up (crawled/discovered curr not indexed) Adjusted HTTP headers Crawl budget / log reviews β SERP Impact AI overview / CTR review Counter content strategy Query count analysis (Devaluation vs slippage) Search appearances
- 06
@jbobbink Β·
I built a Claude skill for Cloudflare's new /crawl API. One API call. Up to 100,000 pages. HTML, Markdown, or AI-extracted JSON. The skill generates code, handles the full async workflow, and ships with 6 SEO-specific crawl configs: β Content audits β Technical SEO crawls β Hreflang validation β Site migration comparison β Incremental monitoring β Structured data extraction at scale It knows when render:false saves you money (free during beta), which resource types to block, and how to use incremental crawling to cut costs. $5/month for 10 hours of browser time. Roughly 12,000 pages. Try beating that with per-page pricing. Skill file in the comments.
- 07
@Charles_SEO Β·
I've said it for a while but the HIGHEST ROI task in SEO using AI isn't creating new content or links, it's UPDATING content! I updated ONE blog post in February using Claude Cowork. It took me under 30 minutes of actual execution time... That single post went from 17 visits/mo to over 2,000 - An 11,000%+ JUMP!!! And Ahrefs is now valuing the organic traffic at $16,700/month π From an old post on an inactive, barely maintained blog... I haven't even LOGGED INTO that blog regularly in over a year. Here's exactly what I did: - Updated the core review sections with current 2026 pricing and service information - Refreshed and added new images throughout (product screenshots, updated pricing tables, real examples) - Hit every freshness signal possible (Meta date updated, "Updated February 2026" snippet at the top, schema dates refreshed, last modified headers) - Expanded the FAQ section and fixed the FAQ schema based on SERP consensus - Added all the missing entities that competing pages were covering but mine wasn't - Expanded the intro with personalization, first-person experience, and the kind of hook that Google's (ENGLISH) NLP systems recognize as "written by someone who actually knows this topic" Every single one of those changes was PLANNED and REVIEWED by Claude Cowork before I touched anything. I gave Claude the current live page, the top 10 direct ranking competitor pages (other blog posts, not service pages) and the current SERP features via the Ahrefs Connector + custom Skills inside Cowork, with a multi-chain approach - And I had the business context + brand voice guidelines already setup in my project. The strategy and analysis took Claude about 10 minutes. The actual execution (me sitting at my keyboard physically making the edits), took under 20 minutes. 30 minutes of work, at least ten thousand dollars in monthly traffic value, on a blog I hadn't touched in over a year. The compound effect of freshness, entity completeness, and schema accuracy on an already-established page is insanely underrated right now! A few targeted updates directed by AI analysis outperformed most of the brand new content campaigns I've watched other SEOs run for months. I've got 200+ blog posts on the site from over a decade of writing. If I carried out this same process on just 10% of those posts, that's a six-figure organic traffic value uplift from content that already exists. I'm running the same audit across PressWhizz's blog next week.. I'll report back on the results. Your old content is probably your most underrated asset, and AI just made it 10x easier to extract the value from it. Stop writing new stuff for a week, go update what's already there, and see how much better results you can get!
- 08
@indexsy Β·
a vet clinic owner built his website off random twitter screenshots, threw it on squarespace, and is somehow already ranking #1 on google. here's the entire local SEO playbook tristan and i broke down to 10x it: the silo structure is the whole game in local SEO. one pillar page for your seed keyword (like "veterinarian"), then you link down to sub-service pages (sick pet visits, wellness exams, vaccinations, parasite prevention) and every one of those links back up to the pillar. this tells google your hierarchy: all these services fall under the one keyword everyone's actually searching. it's the old hub-and-spoke method, but built for service pages instead of blogs, and it works across every local niche, roofing, locksmiths, whatever. service area pages are how you print money outside your google business profile radius. your GBP only ranks you so far, but if you're in newark and people in kearny, bloomfield, and east orange are searching too, you build a separate location page for each service in each surrounding city. tristan tells clients not to be surprised when it's 100-150 new pages. the rule: properly internally linked, unique content on every one so it's not boilerplate. that's how you capture the leads your map listing physically can't reach. the partial-match domain cheat code is still absurdly strong. this clinic ranks #1 organic for "veterinarian new york new jersey" for basically one reason: keyword in the domain + keyword and location in the title tag. that's it. in a low-competition space you don't need many signals to rank, and a partial match domain does a huge amount of the lifting. if you're starting a local business, put the keyword in the name and you're on easy mode. people don't search "veterinarian" anymore, they search the long tail. flea and heartworm meds near me. topical ointment providers. anti-inflammatory medication for my dog. the silo captures all of it because every micro-search has a dedicated page funneling up to the pillar. the businesses only targeting the head term are leaving most of the leads on the table. CRO is where every local site dies and it's a one-shot fix now. this site had no above-the-fold call to action on mobile, no sticky "book appointment" nav, in-content text links nobody clicks. the fix: sticky booking button in your face at all times, contact form above the fold (people who don't fill out immediately are just researching, so give them your process to build trust), and card-style links instead of text links because click data from chrome is a ranking signal now, and nobody clicks an in-content link. all of it is a 10-minute claude job to rebuild and move off squarespace onto cloudflare. citations still matter but quality counts. this guy got 40 citations for $20 and that's basically NGMI tier. the move is bulk high-quality citations (localrank does ~1,000 in one click), and in a space this weak, citations + a behavioral boost alone can put you at #1 before you've even touched the on-site stuff. great for a single-variable case study: change one thing, watch it move. bonus: the moat in local is realer than people think. most vet clinics (and roofers, and dentists) are run by practitioners, not operators, their expertise is treating animals, not building location pages. so if you actually build this structure out, you have a strong moat until a private equity firm buys the clinic down the street. and the agency advice for anyone starting: don't be the general marketing consultant, that's NGMI. carve out one niche, get the exact-match domain ("SEO agency of houston" prints cash), and you can hit $10k/mo in 30-90 days if you're dialed and hungry. the ones who make it are obvious on the coaching calls immediately. full local SEO teardown with @tristanzheng β watch/listen β
Watch video
- 09
- 10
@jakezward Β·
Successful SEO looks like: - 120 new blog posts - 60 high DR backlinks - 500 AI-created pages - 1,000% growth in traffic But remember, it also looks like: - Removing 3 cannibalising pages - Improving a clusterβs internal linking - Tweaking 5 titles for better targeting - Fixing internal links to canonical pages - Writing a featured snippet in 10 minutes - No-indexing low-quality pages in Google - Redirecting a 404 page with 30 backlinks - Creating indexable URLs for 15 sales pages - Adding a new section to an existing blog post Donβt forget to consistently do the little things. They can be just as impactful.
Watch video
- 11
@aleyda Β·
πΈ Agentic Commerce: What SEOs Need To Consider (ACP & UCP) - Excellent analysis by @alexmoss going through: How SEOs must now include the agent as an additional consideration, taking into account that AI agents donβt browse pages but instead query APIs, parse product feeds, and evaluate structured data. Learn about: * Areas to consider for Agentic Commerce Optimization * https://t.co/toxTERq5bE being The Glue * Testing The Agents * What can you do about it now? More! Check it out: https://t.co/evBXVuRXXB
- 12
@MythThrazz Β·
One of the WordPress related things I've shared too little about is: https://t.co/2xW1Wwgplk It started as a cheeky pSEO experiment, but becomes something I'm starting to be really proud of. It's an online WordPress plugin performance lab. My goal is to slowly test ALL of the plugins in the repo (currently 12,5k plugins) Using the same, repeatable tests. So instead of saying: "Plugins BAD. Plugins SLOW!" You can check what kind of performance impact you can expect from each plugin.
- 13
@brodieseo Β·
Technical SEO: when expanding internationally, make sure to keep tabs on your XML sitemaps to keep your indexing reports tidy. This is a very common issue that can occur when businesses expand to new regions and are using multiple domain names for the structure of choice (instead of sub-folders or sub-domains). As a strategic decision, there isn't a "one right answer" for how to execute this expansion, but a downside to using multiple domains often results in missing common issues that inevitably arise over time. Looking at the screenshot on the left β what do you notice? The XML sitemap is hosted on the .com.au but is referencing URLs that are on the .com, being a completely different domain. If there isn't an exact match in regional pages, or if the sitemap itself is a relic of the past (continuing to host an outdated sitemap), this will result in Google unnecessarily trying to discover URLs on the .com that may have issues, resulting in a mass of messy exclusions within the page indexing report in GSC. I've seen this same issue result in URLs being grouped into various different exclusion reports at scale in GSC β common ones being "page with redirect" and "not found (404)", which will understandably happen when cross-domain signals are being sent in this way. The lesson here is to pay attention to the various connective signals across each of your regional domains β whether it be within robots files, XML sitemaps, or hreflang. Regularly testing and paying attention to the page indexing report in GSC will allow you to pinpoint these issues. Note: an important reminder that with large websites, exclusions within GSC are completely normal. The important part is understanding why groups of pages are being flagged, and whether an action should be taken. An action isn't always required.
- 14
@Marie_Haynes Β·
I've seen a lot more sites lately have content shown as "crawled-not currently indexed" in the Page Indexing report in GSC. I wrote a bunch of my thoughts and observations, including an interesting case where a technical reason was the likely cause. However, quality is usually the culprit. This post includes a link to a couple of tools to help you sort through your crawled-not currently indexed report. Hope it helps! https://t.co/nfRJ1jOXJy
- 15
@mehrab_build Β·
I just had a consulting call with a client who had a serious indexing issue. When most people hear "indexing issue" they immediately think it's an authority problem. And they think the fix is buying backlinks. It is an authority issue. But backlinks won't fix it. The real problem was internal linking. And not the surface level stuff. Most people think internal linking just means making sure every page on your site has at least one link pointing to it. That hardly scratches the surface. The most important thing about internal linking is making sure you're passing authority from the right page, with the right anchor text, to the right target page. Every page on your site that's already ranking for something has authority. That authority can be distributed to your other pages through contextual internal links. This is how you help Google understand which pages matter, and get them indexed and ranked faster. But what if none of your pages are ranking yet? Then your first step is finding extremely low KD keywords and writing content around them. Use those pages to internally link to your other new content, also targeting low KD keywords. Slowly build a web of internally linked pages, and work your way up until your entire site is properly connected, all the way to your money pages. Backlinks help. But if your internal linking is broken, you're leaving a lot of authority on the table that you already own.
- 16
@fba Β·
For SEO to work, forget about spray and pray. Change your process, and keep it consistent. Before: prompt β publish After: - Topical map defines what gets written - SEO brief defines the angle, keyword, intent, structure - AI fills the brief, human adds the insight - Internal links connect it to the cluster Same tools. Completely different outputs.
- 17
@aleyda Β·
π Top content tips for authentic, semantic rich content (the type that performs well in AI) by @kmadhavan77 from Microsoft at Friends of Search π 1. Build unique content depth intensity: focus on areas that reflect your expertise, depth and niche problem space 2. Structure is part of story telling: Avoid <div> soup, HTML heading tags to position key points, tables, FAQs, schema 3. Showing your work builds trust: Support your claims with examples, data and sources . Content grounded in evidence builds trust and well anchored claims. 4. Context rules: explain why and when it matters and why to watch for. 5. Freshness is governance: content freshness, consistence update cadence should be part of your content lifecycle management. Bonus: tips for multimodal content π What an actionable, brilliant talk π
- 18
@SEOKeval Β·
SEO agencies that use technical SEO "errors" to convince businesses to work with them are beyond pathetic. Brand I work with got cold emailed a Loom video "auditing" their SEO. Guy in the video goes: "Your meta titles need to be longer." "You have an H3 tag above an H1 tag on this page." "Your blog posts are dated too closely together." Like, bro... Do you even know how SEO works? Fixing these "issues" will have exactly ZERO impact on organic traffic. In fact, I'd argue that 90% of technical SEO is a complete waste of time. Unless the site isn't getting crawled and indexed, suggesting technical SEO fixes as a way to improve a site's SEO is a dead giveaway that you don't know what you're talking about.
- 19
@fba Β·
Stop buying backlinks before you do these 10 things: β’ Build internal links with varied anchor text β’ Fix page speed (a slow site bleeds rankings daily) β’ Drive traffic from social + email to signal engagement β’ Add FAQs to capture rich snippets β’ Create a strategic link from your homepage β’ Add more H2s based on the rankings you already have β’ Add schema markup (takes 10 mins, often ignored) β’ Make your best content accessible from the main menu Do all these first. Then buy backlinks.
- 20
- 21
- 22
@Hartdrawss Β·
SEO Things every Vibe Coder MUST Learn (Extended Edition) 1/ Search Intent > Why someone typed that query. Informational, transactional, navigational. Match it or rank nowhere. 2/ Topical Authority > Covering a subject so completely that Google trusts you as the go-to source for it. 3/ Keyword Clustering > Grouping related keywords under one page instead of creating a new page for every variation. 4/ Long Tail Keywords > Low volume, high intent, low competition. Easiest traffic to win and usually the most valuable. 5/ Programmatic SEO > Using templates and data to publish hundreds of pages at scale. One system, compounding returns. 6/ Core Web Vitals > Google's measure of how fast and stable your page feels. Slow sites rank lower, full stop. 7/ E-E-A-T > Experience, Expertise, Authoritativeness, Trust. Google's framework for deciding who deserves to rank. 8/ Canonical Tags > Tells Google which version of a page is the real one. Prevents you from competing with yourself. 9/ Backlink Profile > Who links to you and how authoritative they are. One strong link beats a hundred weak ones. 10/ Internal Linking > Connecting your own pages strategically. Distributes authority and helps Google crawl your site. 11/ Featured Snippet > The answer box at the top of Google. Structure your content to answer questions directly and win it. 12/ Zero Click Search > User gets the answer on Google without visiting your site. Optimise for brand recall anyway. 13/ Schema Markup > Structured data that helps Google understand your content and display rich results. 14/ Index Bloat > Too many low quality pages dilutes your sites authority. Less indexed pages, more focused ranking. 15/ Crawl Budget > Google wont crawl your entire site every day. Make sure your best pages get crawled first.
- 23
- 24
@glenngabe Β·
New from Gary based on the SOTR podcast covering the topic -> Inside Googlebot: Demystifying crawling, fetching, and the bytes we process Regarding the 2BM limit (which is HUGE btw): "For the vast majority of the web, a 2MB HTML payload is massive, and you will never hit this limit. However, if your page includes bloated inline base64 images, massive blocks of inline CSS/JavaScript, or starts with megabytes of menus, you could accidentally push your actual textual content or critical structured data past the 2MB mark. If those crucial bytes aren't fetched, to Googlebot, they simply don't exist." And some best practics: * Keep your HTML lean: Move heavy CSS and JavaScript to external files. While the initial HTML document is capped at 2MB, external scripts, and stylesheets are fetched separately (subject to their own limits). * Order matters: Place your most critical elements β like meta tags, <title> elements, <link> elements, canonicals, and essential structured data β higher up in the HTML document. This ensures they are unlikely to be found below the cutoff. * Monitor your server logs: Keep an eye on your server response times. If your server is struggling to serve bytes, our fetchers will automatically back off to avoid overloading your infrastructure, which will drop your crawl frequency. https://t.co/kYyzCHh5Tr
- 25
@aigleeson Β·
SEO is dead. Google, OpenAI, and Perplexity don't rank pages anymore. They write answers. The University of Toronto just published the first real blueprint for this shift. It's called GEO (Generative Engine Optimization) and it changes everything about how visibility works. Here's what their experiments found: β AI search ignores your blog and social posts almost completely β ChatGPT and Claude barely show brand pages, Google still does β Language and phrasing shift what gets cited across regions β Big brands dominate unless you build verifiable third-party authority The fix: β Engineer your site for machine scannability (schema, structured data) β Get cited by authoritative reviewers and publications β Build local-language authority, every region's AI runs on different media β Treat your website like an API, not a brochure Stop optimizing for clicks. Start optimizing for citations. The brands AI trusts will own the next decade of traffic. Everyone else is building for a search engine that's already dying.
- 26
@Hartdrawss Β·
Just hit these numbers on a client Next[.]js build today ??!! LCP 0.40s. CLS 0.06. INP 8ms. heres exactly how i got there: [ step 1 β rendering strategy ] - most devs default everything to SSR and move on completely - that's poor strategy tbh; every route needs a decision. does this page change per user? - we mapped every route before writing a single component - this alone cuts your server response time significantly and it's quite a difference [ step 2 β nothing blocks the fold ] - went through every script loading above the fold like tracking scripts, font loaders, analytics - the browser should paint the page before it does anything else - Hard re-work but was able to clean it up; lazy loaded all of them so they only fire after the page fully paints [ step 3 β SEO infrastructure on day one ] - schema markup, OG tags, sitemap, robots.txt done and knocked out before any feature - crawl structure mapped properly so that google can actually index the right pages [ step 4 β assets compression ] - every image converted to webp, sized for the containers and a s3 integration - fonts subset to only the characters being used - videos compressed hard before the first commit TLDR; performance and SEO aren't a sprint you run before handoff but rather the foundation everything else sits on. if your site isn't ranking or loading slow on mobile don't blame the content !
- 27
@SEOKeval Β·
Found an absolutely mind-boggling technical SEO issue the other day. A brand I just started working with doesn't have their meta titles displaying correctly. Google is pulling URL of the page as the meta title instead. How this brand's previous SEO agency never caught this, I have no idea. But the meta title is literally the most most important on-page SEO factor. You cannot rank a page without an optimized meta title. It's no wonder this brand barely ranks for any keywords. I'm going to fix the issue this week. And I'll provide an update so you can see how drastically this improves their SEO.
- 28
@natmiletic Β·
Google doesn't care what CMS you use. It cares if your site is slow, has broken links, or serves a terrible mobile experience. WordPress, Webflow, Framer, headless... doesn't matter. Performance and authority matter. Your "old school agency" warning about platform migrations tanking SEO? That's usually about botched redirects and lost content, not the tech stack itself.
- 29
- 30
@RobHoffman_ Β·
don't buy into the hype on X that spamming SEO articles with Claude will get you traffic/leads. our SEO client made $180,000 last month and we didn't create any new pages. We just optimized their site architecture. here's how: the client is a managed IT and security compliance company. the problem: they were trying to rank for everything at once: managed IT, security compliance, and more, with no clear hierarchy between them. here's how we fixed that and got their money pages ranking: 1. Focused the homepage on their most valuable keyword: "managed IT service provider" 2. Created dedicated pages for their core compliance and security services 3. Rebuilt the heading hierarchy to signal topical relevance 4. Rewrote entire sections of content to read like a buying page, not a blog post 5. Added a localized "Why Choose Us" section to their content for trust 6. Built an FAQ section covering both branded and unbranded high-funnel queries 7. Used Mentions to see what phrases were getting the most AI visibility, then optimized their content around those to rank in LLMs (that last one matters more than most people realize). The lesson: before you publish more pages, make sure your site is optimized.
- 31
@omarships Β·
Most people shouldnβt be doing pSEO. If Google isnβt indexing or prioritizing your current pages, adding 10k more just dilutes your site. Most sites already struggle with: β’ pages not getting indexed β’ low crawl priority β’ weak internal linking Scaling that = scaling the problem. pSEO only works when: β’ your domain already has authority β’ your key pages are consistently indexed β’ internal links actually pass and concentrate that authority Otherwise youβre just creating thousands of invisible pages and killing your website.
- 32
@natmiletic Β·
The "Crawled, currently not indexed" nightmare π± 1. Thin content (yes, even if it's "unique") 2. Duplicate structure across pages 3. Slow load time or broken mobile experience 4. Internal linking that buries the page 5. Low engagement signals if it was indexed before Authority matters, but these kill indexing even on strong domains.
- 33
@gaganghotra_ Β·
Enterprise technical SEO - if over time there is a build up of millions of redirected URLs and 404/410 BUT still Google keeps on fetching those even after years of that change implementation. What can be done? cuz almost 36% of monthly Googlebot fetches are those URLs which I think is eating into the crawling budget for other important URLs. @patrickstox @MalteLandwehr @Hobo_Web would love to hear your thoughts on this - thanks π
- 34
@semrush Β·
Google just drew a clear line around AI search optimization: itβs SEO. On May 15, 2026, Google published its official guide, βOptimizing your website for generative AI features on Google Search.β John Mueller announced the release on the Google Search Central Blog, and Google added a new βGenerative AI fundamentalsβ section to Search Central documentation. The biggest takeaway: if your content doesnβt meet the quality and technical standards needed to rank in traditional search, it wonβt win visibility in AI-generated answers either. Google also shut down several popular GEO tactics. According to the guide, SEOs can ignore llms.txt files, AI-only rewrites, content βchunking,β and special Markdown or schema implementations built solely for generative AI visibility. The broader message is even bigger: Google frames AEO and GEO as extensions of SEO β not separate disciplines with separate playbooks. AI visibility runs on the same foundations: strong technical SEO, authoritative content, and clear site structure. Learn more: https://t.co/Eo8oFgg5Lz.
- 35
@foley_seo Β·
Google is indexing LESS content year by year, their threshold for indexing content has gone up significantly. Why? 1. It costs money to store and process website data 2. It doesn't need 10,000 URLS with the same copy 3. It makes no sense to index something you are unlikely to serve (quality issues, trust issues etc) So, I put together a FULL guide on using Google's URL inspection tool. If you aren't using it but you are in SEO, you should be using it. π‘² Periodically check power pages on a domain to check index state π‘² Check indexing states π‘² Address and deal with anomalies π‘² Request indexing for pages where issues have been fixed π‘² Check rendered outputs (screenshot / HTML) π‘² Check canonical profile and so much more. I've done a video which walks you through Google's URL inspection! Enjoy https://t.co/XfJm0q4IkT
- 36
@Joey_Walker82 Β·
What a manic morning at home! Most of the daily chores done now and manged to get in 40 replies on X done plus this new SEO feature for CTRLoop I wanted a way to get more exposure through SEO as there was only 8 accessible pages to be indexed. So I have now created the Niche Directory. A tailored page on what works and what doesn't for that niches thumbnails. Seeing as there are what feels like infinite niches for YouTube I have quickly added another 40 pages just to start with, with the aim of expanding to over 1000 in the next few weeks.
Watch video
- 37
@pasha_barbashin Β·
My pages were not indexed - here's what actually worked π I automated SEO blog posts: keywords, creation, publishing. Complete waste of time. 0 pages indexed. I tried 5-6 fixes. Nothing. Until I did this: Go to GSC β URL Inspection β paste URL β request manual indexing
Watch video
- 38
@woocassh Β·
Thursday Technical SEO Tip Page load times matter! π RankGoat keeps track of the performance of my websites overtime using Lighthouse, you can easily do it manually but when you have multiple websites it becomes a pain, and it's easy to forget today it highlighted a few issues that were affecting mobile device performance and load times on itself https://t.co/Ey4XdLEygt I plugged them into claude and the site now loads almost instantly from 99/92 to 100/100 (desktop / mobile) the big (embarassing) issues I had: - 3rd party confetti library loaded on each page but only used on successful signup (no self hosted and minified) - CDN hosted fonts (now self hosted) - using gzip on css as well as html in nginx now so the payload is much smaller also claude naturally ads stuff as you vibe code so its important to keep track of this over time! wishing you more clicks on this fine Thursday!
- 39
@AIwithArsalan Β·
I tried Perplexity Computer on a full SEO audit workflow today, and this is where it started feeling genuinely useful. Instead of jumping between different tools, tabs, and spreadsheets, I had it work through the full audit flow, from spotting technical issues and on-page problems to surfacing missed opportunities and prioritizing what should actually be fixed first. Thatβs what stood out to me. It didnβt feel like getting random SEO advice. It felt more like turning a messy audit process into something much more structured and usable.
Watch video
- 40
@Aevmorfop Β·
Not sure this counts as marketingβ¦ but I went deep on SEO today. Turns out Iβd managed to break it at some point, while I was doing another SEO audit π€¦ββοΈ I was setting things up so Google could see all the βSEO stuffββ¦ but turns out, the same script, was stripping out all of the actual contentπ So from the outside, the site looked fine... but to Google, it was basically empty. No wonder impressions were going nowhere π¬
- 41
- 42
- 43
@bekircagricelik Β·
I had 22 blog posts on my site. Google indexed zero of them. Turns out a single wrong canonical tag was telling Google every post was a duplicate. 22 blog posts, completely invisible. Fixed one line of HTML. All 22 entered the indexing queue. Now included this in the @clearauditapp SEO check. Check yours. This bug is silent.
Best Tweets by Topic