AI 资讯

1.4 billion iPhones. That's how many devices Apple will push Siri 2.0 to this fall—built on a custom 1.2-trillion-parameter Gemini model and an Extensions system that lets users route Siri's AI brain to Claude, ChatGPT, or Google's own Gemini directly. Tim Cook announced all of it at WWDC 2026 on June 8, his final WWDC keynote before handing the CEO role to hardware chief John Ternus in September. The story isn't just a better Siri. Apple is opening iOS as an AI distribution channel—the largest in history—and the developer implications are immediate. The Gemini Deal Apple licensed a custom 1.2-trillion-parameter Gemini model from Google at a reported $1 billion per year. That's eight times the parameter count of Apple's current 150-billion-parameter on-device foundation model. Bloomberg first reported the deal in March 2026; WWDC confirmed it on stage. The private vs. cloud distinction matters here. Apple isn't routing your queries to Google's servers. The custom Gemini model runs on Apple's Private Cloud Compute (PCC) infrastructure—Apple-owned silicon, Apple-controlled software, with cryptographic attestation that prevents even Apple engineers from reading query contents. This is the same architecture Apple built for existing cloud AI features, now scaled up for a model eight times larger. What that means in practice: Siri can answer complex multi-step questions, reason over your personal context (calendar, messages, mail), and execute cross-app actions. None of it touches Google's data centers. The New Siri App Siri in iOS 27 ships as a standalone app. iMessage-style interface, persistent conversation threads, full chat history synced via iCloud. Two modes: quick invocation through the Dynamic Island (a glowing "Search or Ask" prompt) for fast queries, and the full chat app for extended conversations. Chat-mode Siri is a first-party ChatGPT competitor. Persistent threads, file attachments, on-screen awareness. Ask "what does this error mean?" while looking at an

Clean Architecture on the Frontend: Beyond Smart and Dumb Components djblackett djblackett djblackett Follow Jun 7 Clean Architecture on the Frontend: Beyond Smart and Dumb Components # react # frontend # architecture # typescript Comments Add Comment 14 min read

The signal hidden in this week's GitHub trending Two agent-shaped repositories cracked the daily GitHub trending board this week. The first is mvanhorn/last30days-skill , a Claude-style skill that researches a topic across Reddit, X, YouTube, Hacker News, and Polymarket, then synthesizes a grounded summary. The second is NousResearch/hermes-agent , billed as "the agent that grows with you" — a persistent agent runtime that compounds context across sessions. Both ranked the same week. Both are skill-shaped: a manifest, a trigger, a set of instructions, and a runtime expectation. This is the first time I have seen two skill repos chart simultaneously on GitHub trending. Most observers will treat them as cool side projects, fork them, star them, and move on. They are cool side projects. They are also a phase transition that the agent ecosystem has been edging toward for nine months. By Q4 you are going to wish you had read this signal in early June, because the dependency-graph problem about to land in production agents is the same one the npm ecosystem ran into between 2011 and 2018 — except faster, less tooled, and with a much larger blast radius. This post is about that phase transition. The benchmark coverage of skills is everywhere; what you cannot easily find is a working operational model for managing them at fleet scale. I am going to give you one. What actually shipped this week Let me anchor on the facts before I extrapolate. last30days-skill (mvanhorn) is a single skill bundle. Its SKILL.md tells the host agent: when the user asks for recent news, controversy, or sentiment on a topic, run a structured multi-source fetch — eight queries minimum, across five platforms, with a freshness window of 30 days — then synthesize. The skill ships with prompt scaffolding, query templates, and a synthesis rubric. It is roughly 600 lines including instructions and helper scripts. Installation is a git clone into your skill directory, no package manager, no version negotia

Here's the maths most calculators get wrong Most freelance rate calculators are wrong. Not buggy — conceptually wrong. They take your income goal, divide by hours, and hand you a number that will quietly lose you money all year. I got tired of explaining the correct calculation to freelancer friends, so I built a tool that does it properly. Here's the logic behind it, and a bit about how I built it. The flawed formula The typical calculator does this: hourly_rate = annual_income_goal / annual_hours_worked So if you want $80,000 and work 2,080 hours a year (40 × 52), it tells you to charge ~$38/hr. This is wrong in three separate ways. Fix 1: Tax is not optional Your income goal is a net number — what you want to keep. But you're taxed on gross. So the first correction is grossing up: const grossIncome = netTarget / ( 1 - taxRate ); // $80,000 / (1 - 0.28) = $111,111 That's already a $31,000 gap the naive formula ignores. Fix 2: You don't bill every hour you work This is the big one. Freelancers bill roughly 55–65% of their working hours. The rest is admin, proposals, invoicing, sales calls, and learning. const totalHours = weeksWorked * hoursPerWeek ; // 46 * 40 = 1840 const billableHours = totalHours * billableRatio ; // 1840 * 0.6 = 1104 So your real billable capacity isn't 2,080 hours. It's closer to 1,104. Pricing on the wrong denominator is how people end up working 50-hour weeks and still missing their income target. Fix 3: Business expenses come out of gross Software, hardware, insurance, courses — all real costs that need covering before you pay yourself: const totalNeeded = grossIncome + annualExpenses ; The corrected formula Putting it together: function minimumRate ({ netTarget , taxRate , expenses , weeks , hoursPerWeek , billableRatio }) { const gross = netTarget / ( 1 - taxRate ); const totalNeeded = gross + expenses ; const billableHours = weeks * hoursPerWeek * billableRatio ; return totalNeeded / billableHours ; } minimumRate ({ netTarget : 80000 ,

If you’ve ever spent hours debugging slow EC2 workloads or getting sticker shock from unexpected EBS IOPS charges, you’ve probably wondered if there’s a better storage option for temporary, high-performance data. AWS EC2 Instance Storage (also called Instance Store) is one of the most underutilized but powerful tools in the EC2 ecosystem—if you know how to use it correctly. This guide breaks down everything you need to know: core concepts, performance optimizations, use cases, limitations, and how it stacks up against EBS. By the end, you’ll be able to cut storage costs, boost workload performance, and avoid costly data loss mistakes. Table of Contents What Exactly Is AWS EC2 Instance Storage? Core Concepts of EC2 Instance Store Key Features That Make Instance Store Stand Out Which EC2 Instance Types Support Instance Store? Deep Dive: NVMe SSD Instance Store Volumes SSD Instance Store Performance Best Practices EC2 Instance Store vs EBS: Head-to-Head Comparison Top Real-World Use Cases for EC2 Instance Store Critical Limitations to Avoid Costly Mistakes Production-Grade Best Practices for Instance Store Root Volume Options: EBS-Backed vs Instance Store-Backed Instances EC2 Instance Store Pricing: No Hidden Costs Conclusion References What Exactly Is AWS EC2 Instance Storage? EC2 Instance Store is temporary block-level storage that is physically attached to the host server running your EC2 instance. Unlike standalone storage services like EBS, EFS, or S3, it is part of the EC2 service itself, with no network overhead between your instance and the storage disks. Its defining trait is its ephemeral nature: data stored on Instance Store only persists for the lifetime of the associated instance. If you stop, hibernate, or terminate your instance, all data on Instance Store volumes is permanently deleted. Core Concepts of EC2 Instance Store Before you start using Instance Store, make sure you understand these foundational rules: Device naming : Instance Store volumes are

PostgreSQL Error 2200D: invalid escape octet The 2200D: invalid escape octet error occurs in PostgreSQL when a bytea value contains an invalid escape sequence. This typically happens with the legacy escape format for binary data, where octet values must be represented as three-digit octal numbers in the range \000 to \377 . If the escape sequence falls outside this range or uses non-octal digits, PostgreSQL raises this error immediately. Top 3 Causes 1. Out-of-range octal values in bytea escape literals The bytea escape format only accepts octal values from \000 to \377 (decimal 0–255). Using values like \400 or non-octal digits like \9 will trigger this error. -- BAD: \400 exceeds valid octal range (max is \377) SELECT E ' \\ 400' :: bytea ; -- ERROR: invalid escape octet -- BAD: \9 is not a valid octal digit SELECT E ' \\ 9AB' :: bytea ; -- ERROR: invalid escape octet -- GOOD: valid octal escape sequences SELECT E ' \\ 377' :: bytea ; -- decimal 255 SELECT E ' \\ 101' :: bytea ; -- 'A' character SELECT E ' \\ 000' :: bytea ; -- null byte 2. Using escape format strings with hex output format Since PostgreSQL 9.0, the default bytea_output is hex . Applications that mix hex -format output back into escape -format input processing can generate malformed escape sequences. -- Check current bytea output format SHOW bytea_output ; -- GOOD: Use hex format (recommended for all new projects) SELECT ' \x DEADBEEF' :: bytea ; SELECT ' \x 48656C6C6F' :: bytea ; -- 'Hello' -- GOOD: Use encode/decode for safe conversions SELECT encode ( ' \x DEADBEEF' :: bytea , 'hex' ); -- output as hex string SELECT encode ( ' \x DEADBEEF' :: bytea , 'base64' ); -- output as base64 SELECT decode ( 'deadbeef' , 'hex' ); -- hex string → bytea SELECT decode ( 'SGVsbG8=' , 'base64' ); -- base64 → bytea 3. Incorrect escaping during data migration or manual SQL When migrating binary data from other databases (Oracle, MySQL) or writing raw INSERT statements manually, developers often confuse octal and

Your agent nailed every test case. You shipped it. Within 48 hours, users report hallucinated outputs, silently dropped tool calls, and responses that bear zero resemblance to what worked on your machine. You reload the same prompt locally. It works perfectly. Welcome to the most predictable failure mode in AI engineering: the dev-to-prod gap. This is Crucible C01. We dissect the five failure modes that kill agents in production and give you the tools to catch them before your users do. The Idea (60 Seconds) Developers test agents in idealized conditions: deterministic inputs, warm context windows, generous API latency budgets, and sequential tool calls. Production exposes the opposite environment: cold starts strip context, rate limits compress timing, and parallel calls introduce race conditions. The agent that performed flawlessly at temperature 0 on a 2k-token context window collapses at temperature 0.7 on an 8k-token window. The five failure modes are temperature drift and context window overflow first; silent API errors and prompt drift follow; race conditions complete the set. Each one has a detection pattern and a fix, and this article delivers both plus the CLI tool to automate the detection. Why This Matters AI agent failures differ from traditional software failures in one critical way: they are stochastic. A web API either returns 200 or 500. An AI agent returns something that looks plausible 90% of the time and is catastrophically wrong 10% of the time. That 10% is invisible in manual testing and devastating in production. The economics compound fast because every failed agent interaction wastes tokens, and wasted tokens cost money. At scale, a subtly broken agent burns budget faster than a working one because it retries, loops, and rephrases instead of succeeding. A single temperature drift bug can double your API spend. Reliability is the differentiator. The market is flooding with AI wrappers. The ones that survive will be the ones that work consiste

OpenAI launches the Economic Research Exchange to study AI’s impact on jobs, productivity, and the economy. Applications are now open for selected research projects.

I haven't written articles in quite a while and I recently decided to come back to it. At work I use AI daily, so a big part of my coding tasks are delegated to agents. I try not to do the same when it comes to writing text but I don't have a clear reason for that (or maybe I do and I don't want to admit it). I am sure people can take advantage of generating text with the help of AI but at the moment I feel like prompting would not save me any time and writing the text myself would be faster. What about you? Are you using AI to write your articles? Image credit - jessica olivella, on pexels

It's 2am. A pipe just let go behind a kitchen wall and water is coming through the ceiling into the room below. The homeowner is standing in the dark in a panic, phone in hand, Googling "emergency plumber near me." They tap the first number. It rings four times and drops to voicemail. They don't leave a message. They tap the second number. You were the first number. You were asleep. And you just lost the most profitable job you'd have booked all week to whoever picked up on the second ring. This is the part of running a plumbing business that nobody puts on a P&L. The call that matters most arrives at the exact moment no human is there to answer it. And in plumbing, unlike any other trade, that's not the exception. It's the majority of the work. Plumbing's problem is different from every other trade An HVAC shop bleeds during summer rush. A roofer loses jobs to slow follow-up over a three-week sales cycle. Plumbing is its own animal, because plumbing is emergency-driven, and emergencies don't keep business hours. Industry call-tracking data tells the story. Depending on the source, anywhere from 40% to over 70% of home-service calls land outside the standard nine-to-five window, and for emergency-driven trades like plumbing it skews to the high end of that range. Either way the takeaway is the same. A huge share of your inbound isn't coming in while someone's at the desk. It's coming in at night, on a Saturday, on Thanksgiving morning when a basement is filling with sewage. If you're staffed to answer the phone nine to five, you are structurally set up to miss a large slice of your own demand. Not because you're doing anything wrong. Because the work shows up when the lights are off. And here's what makes it brutal. The after-hours emergency call isn't just any job. It's your best one. Why the missed emergency call costs more than the tech A routine daytime service call, a dripping faucet, a running toilet, runs a couple hundred dollars and the customer is happy to

The Letter VCs Are Quietly Deleting from ARR Startups are reporting revenue they haven't earned yet. VCs know it. Investors are cheering anyway. We've seen this movie. You're evaluating an AI startup. The pitch deck shows $100 million in ARR. The growth curve is parabolic. The deck says they signed $100 million. What it doesn't say is that $70 million of that is "committed ARR": contracts signed but not yet invoiced, customers who haven't deployed yet, pilots that count toward the number if they convert. Subtract the gap and you've got $30 million in actual recognized revenue hiding under a $100 million headline. This is the ARR inflation playbook, and it's running at full speed right now. The Trick Has a Name "CARR" stands for Contracted or Committed ARR. It's a legitimate concept. In industries where revenue accrues slowly after contract signing (healthcare AI deployments, energy optimization platforms, multi-year enterprise integrations), the gap between signature and recognition can legitimately take months or years to close. Reporting CARR alongside ARR, properly labeled, is defensible. That's not what's happening. What's happening is simpler: founders strip the "C" and just call it ARR. One VC told TechCrunch the gap between CARR and actual ARR can run as high as 70% [1]. In some confirmed cases the spread is 3-5x. Another investor said flatly: "For sure they are reporting CARR as ARR" [1]. The article indicates that the investor community is not only aware, but many are actively complicit. The logic follows its own warped rationality. When one startup in a category inflates, the others have to follow to stay competitive for talent and headlines. "When one startup does it in a category, it is hard not to do it yourself just to keep up," as one investor put it [1]. Spellbook CEO Scott Stevenson, one of the few willing to call this in public, described the practice as a "huge scam," adding that major VC funds are not just watching it happen but actively supporti

Including, me. There’s no question the world has experienced significant change, over just the past 10 years. You’ve got standard concerns like AI; questions around whether tech is helping or hurting us - but I want to present another side to the story: one that I’ve got direct experience in. In a new “series” I’ll be rolling out, I’ll be deep diving into my prior experience as a software engineer in this new world where everything is a metric to be improved. Laying out the problem Not to be vague, I’ve referenced the problem in the title. Companies, and by proxy, engineers at the companies, are being driven (by shareholders), to ensure you maximise the time spent on their platforms. Perhaps, that much is apparent and obvious. But, have you stopped to think recently how vehement and aggressive these practices are getting? How many services do you use or rely on that are (subtly or not), making decisions purely just to increase the time customers spend with the software open ? I’m a big believer that software can make lives better . I’ll be quick to announce, though, that as of 2025, there’s a lot of secrecy behind the scenes around why companies are striving harder to hit engagement metrics. It’s a race to the bottom, and as we continue seeing software take up more and more of our time spent, it’s worth exploring just how bad things can get when you’re laser focused on app enegagement. Making something good, isn’t good enough I worked at Flux Finance for 3 and a half years, before unfortunately being made redundant. Flux went on, only months later, to be bought out by Networth. Not terrible; acquisition complete, and everybody’s clapping. As a refresher, Flux was an app designed to make your money journey easier, and make you more financial literate, in fun ways. The motto: “helping 400k+ Aussies win at money ” - with gamification being a major aspect. For Australians, it features: a way to check your credit score articles released regularly to learn about money new

LLM-powered Learning, Handwritten Digit Recognition, and AI Career Guidance Today's Highlights This week's top stories showcase practical AI applications: an LLM-powered tool for domain learning, a cloud-enhanced handwritten digit recognition system, and an AI-driven career guide. These projects demonstrate how AI frameworks are being applied to real-world workflows, from knowledge acquisition to personalized advice. Show HN: Lathe – Use LLMs to learn a new domain, not skip past it (Hacker News) Source: https://github.com/devenjarvis/lathe This project, Lathe, presents a novel approach to leveraging Large Language Models (LLMs) not just for quick answers, but for deep, structured learning within a new domain. Unlike traditional LLM interactions that might encourage skipping detailed research, Lathe aims to facilitate a more profound understanding by guiding users through a systematic learning process. It likely employs advanced retrieval augmentation generation (RAG) techniques, potentially combined with iterative prompting strategies and graph-based knowledge representation, to help users build a comprehensive knowledge base on a chosen topic. The framework focuses on transforming raw information into actionable insights and structured learning paths. This makes LLMs a powerful study aid, enabling domain experts or newcomers to grasp complex subjects more efficiently by providing tools for semantic search, concept mapping, and progressive knowledge acquisition, moving beyond simple question-answering into true assisted learning workflows. Comment: This is precisely what's needed for complex enterprise knowledge management – turning LLMs into an active learning partner, not just a summarizer. I'd explore how it structures knowledge graphs or progressive learning paths. Handwritten Digit Recognition System with Cloud and AI Enhancements (Dev.to Top) Source: https://dev.to/yohannesah/handwritten-digit-recognition-system-with-cloud-and-ai-enhancements-i4e This project

This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built The average student opens their notes 3 days before the exam. The above average student opens them the night before. Either way, they both end up on YouTube at 3am watching a guy explain thermodynamics with a whiteboard and too much energy. I built something better. I built Forge AI — a collaborative AI study platform that turns your lecture notes, PDFs, and YouTube links into a full study session with an AI tutor that actually talks back. Here is what it does: 📄 Upload your notes or paste a YouTube link — Forge AI reads everything and builds you a prioritised study plan in seconds. 🧠 Deep Dive into any topic — get full AI generated study notes, a mnemonic memory trick, and a built-in quiz. 🎙️ Talk to your AI tutor live — it listens, speaks back, and you can see the transcript building in real time as it talks. 👥 Create a Forge Room — invite your study group, ask the AI questions together, battle each other in a live quiz, and everyone sees everything at the same time. It started as CrammAI . A solo study tool I built under exam pressure. Well, it could generate a study plan from your uploaded files and quiz you on topics. That was it. No voice. No collaboration. No rooms. No Finesse. Just you, alone, cramming at 2am. Five months later I came back to finish it. The result is Forge AI. Demo Live app GitHub Here is what Forge AI can do: 1. Upload your materials and pick your mode Three modes based on how much time you have: 🧘 Cruise Control — 1+ week until exam 🚀 Turbo Mode — 2 days left ⚡ Zoom Mode — due tonight 2. Paste a YouTube link — it transcribes automatically ts export const apiFetchYoutubeTranscript = async ( url : string ): Promise < string > => { const videoId = extractYoutubeId ( url ); const response = await fetch ( `/api/transcript?videoId= ${ videoId } ` ); const data = await response . json (); return data . transcript ; }; No manual transcription. Paste the link, Forge AI pull

I'm starting a new project. It's the most ambitious thing I've attempted from a phone. The goal: an AI agent that controls a smartphone. It opens apps, navigates screens, taps buttons, types text, and completes multi-step tasks. All offline. All local. No cloud. This is Day 1 of a public build log. No fluff. Just what I'm building, how it works, and what breaks along the way. What I'm Building An autonomous AI agent that runs entirely on an Android phone. You give it a command in plain English: · "Open WhatsApp and message Mom I'll call later." · "Search for Kotlin jobs on Wellfound." · "Open my notes and summarize what I wrote yesterday." The agent parses the command, plans the steps, and executes them—opening apps, finding the right buttons, typing text, hitting send. No cloud. No API keys. Just a phone that acts on your behalf. The Stack Component Tool AI Brain Gemma 4 E4B (local, via Ollama) Runtime Termux (Linux on Android) Phone Control ADB + UI Automator Orchestration Python Why This Matters Most AI agents live in the cloud. They need internet, APIs, and someone else's server. A local agent that runs on a phone means: · Privacy: your data never leaves your device. · Offline: works even without internet. · Accessible: built for the device billions of people already own. The Hard Parts I Already See · The agent needs to "see" the screen to know where to tap. Text detection is doable. Image-based buttons are harder. · Multi-step tasks need verification. If one tap misses, the whole chain fails. · Android permissions. ADB requires developer mode. A user-facing version would need a workaround. What's Next · Day 2: Create the repo. Set up the project structure. Push the first working script. · Day 3: Get screen text detection working with OCR. · Day 4: Test a full 3-step task. This is Day 1. The repo goes live tomorrow. Follow along if you want to see something rare get built from scratch.

Launch week for a side project means the same chore every time: export the logo, open Figma, create artboards for LinkedIn (400×400 and 4200×700 cover), Google Business Profile (1200×1200 JPEG with a minimum file size or Google rejects it), YouTube (2560×1440 with a safe zone nobody remembers), Open Graph (1200×630), Instagram (circle crop), Discord, TikTok… Design tools are great at making brand assets. They are slow at batch-exporting exact platform specs — especially when encoding rules differ (PNG vs JPEG, max KB, min KB for GBP, center-right vs YouTube-safe positioning). So we built a small free tool: one SVG or PNG in → 21 platform files out. What it actually does Upload a logo. Pick categories (or take everything): 8 profile icons — mark-only, padded for circular crops (LinkedIn, X, GBP, Facebook, Instagram, YouTube, TikTok, Discord) 2 profile lockups — logo + wordmark for LinkedIn company and GBP 7 banners/covers — including LinkedIn 4200×700, YouTube safe-area channel art, Facebook cover under 100 KB target, Open Graph 1200×630 4 post sizes — Instagram square/portrait/story, Pinterest pin Outputs are PNG or JPEG per platform rules. White background. ZIP download. Why not Canva? Canva is excellent for templates and marketing creatives. For “I already have a logo, give me every official size,” you duplicate frames and export manually — often behind a paid tier for brand kits and bulk workflows. This tool does one job, free, no account: 👉 https://varnox.io/tools Longer write-up with platform gotchas (GBP min JPEG size, YouTube safe area, etc.): 👉 https://varnox.io/blog/free-social-media-logo-size-generator Privacy (because it’s your logo) SVG uploads sanitized before render Generated files expire after 30 minutes — nothing permanent stored No signup We use the same catalog internally when onboarding clients onto GBP + LinkedIn + OG tags. Shipping it publicly was easier than answering “what size is our Facebook cover again?” for the fifth time. Stack note (for

Three years ago we had our first real outage. Six hours of downtime. Thousands of angry users. Multiple executives on the call. Here's what we did right, what we did wrong, and what we'd do differently. What we did right 1. Communicated immediately. The moment we knew we had a problem, we updated the status page and emailed our biggest customers personally. Not when we had answers. When we had a question. 2. Had a single incident commander. One person making calls. Not a committee. When the CEO tried to direct technical work, the IC politely rerouted and told her where her help was actually needed (talking to customers). 3. Took care of our people. During hour 4, I ordered food. During hour 5, I forced the primary engineer off the call for 20 minutes to walk outside. Long incidents destroy people. You have to feed them and force them to rest. 4. Wrote it down as we went. We had a shared doc with a live timeline. When the post-mortem came, we had every decision captured. What we did wrong 1. Tried to fix the root cause during the incident. For the first 2 hours, we were digging into why the database was struggling. We should have been mitigating (rolling back) first. 2. Let too many people 'help.' By hour 3, we had 12 engineers in the call. Half of them were useless. The IC should have kicked people out sooner. 3. Gave optimistic estimates. 'We'll be back in 30 minutes.' We were not back in 30 minutes. That miscommunication was worse than saying 'unknown.' 4. Didn't prepare the executive communication. The CEO had to answer customer questions in real time with no script. We should have drafted talking points for her after hour 1. What we'd do differently Mitigate first, investigate second. Always. Cap the number of active engineers at 4 during an incident. Others go on standby. Default to 'unknown' for estimates. Only give a number when we're sure. Assign someone explicitly to 'executive liaison.' Their job is to keep the C-suite informed without interrupting the tec

We run 10+ web products. For years our SEO tooling was a $100+/month subscription we mostly used for one job: technical audits. The keyword and backlink dashboards sat untouched while the bill renewed every month. At some point the math stopped making sense, so we rebuilt our stack around what we actually use. Here's the honest breakdown — what we kept free, what we replaced, and why. What a technical audit actually needs to check Before picking tools, it helps to know what you're auditing. The technical layer is finite and well-defined: Crawlability — robots.txt, broken internal links, redirect chains Indexability — noindex tags, canonical correctness, soft 404s, orphan pages Sitemaps — only canonical, indexable, 200-status URLs On-page — titles, meta descriptions, one H1, valid structured data International — hreflang reciprocity (if you're multilingual) Performance — Core Web Vitals (LCP, CLS, INP) That's it. None of it requires a keyword database or a backlink index — the two things you're really paying $100+/mo for in the big suites. The free tools that cover most of it Google Search Console is non-negotiable and free. The Pages report is the source of truth for what's indexed and why the rest isn't. PageSpeed Insights (free) gives you real Core Web Vitals. Screaming Frog's free tier crawls up to 500 URLs, which is plenty for small sites. For a long time that was our whole stack: GSC + PageSpeed + free Screaming Frog. If your site is under 500 pages, you may not need anything else. Where it broke down for us The free Screaming Frog cap (500 URLs) is the wall. Several of our sites are bigger, and re-auditing them meant either the paid Screaming Frog licence (annual) or going back to a monthly suite. Both felt wrong for something we run after every deploy. So we built our own crawler for the technical layer — and then, honestly, turned it into a product because other people we talked to had the same problem. It does the whole checklist above across the entire sit

If someone asked one of the know AI chats for feedback on body, would it be honest or be supportive only submitted by /u/thowing_away48494578 [link] [留言]