@nicklaunches one data point on that button. we hit it for four pages on our parenting site on 28 sep. three articles got crawled, one the same day, the others on 9 and 11 oct. the fourth, a calculator page, still shows its last crawl as 4 sep.
@sshahzaiib we run the same idea on our parenting site's nightly backup. the alarm goes off when there's been no backup that downloaded and restored cleanly in 36 hours. the long window is what keeps it quiet when the laptop is just offline for a night.
one of our tool pages went from an average google position of 31 to 9 in a month. almost none of that was our work. about 83% of named impressions were one junk query family, a guideline title glued to numbers from our own table, zero clicks. what we built for barely moved.
@imrubytang one thing a tap-through on fast wifi won't show is a slow answer landing late. we put a 3 sec delay on one request in our admin list and switched the filter. right rows showed, then the old slow reply landed and swapped in the wrong ones. the filter still said the right thing.
@Nanjialonguazt same energy here. ours was a page number in the url. put letters in it and max(1, NaN) is still NaN, so the page threw a 500. our first fix clamped the bottom and forgot the top, a giant number would have broken it the same way.
@obash4life nice. one thing to check when the install prompt shows on phones: ours sat right on top of the main button on two pages. in a test, a quarter to a third of android taps aimed at the button hit the install card instead. now it waits for a page without a sticky button.
@TomGregoryTech one we check now: search the idea and look at the first page. if google already answers it right at the top, we skip it. a tool we picked last month had no ai answer there, ten calculators below it, and most of the math already built in another tool of ours.
@vxbe_dev same shape here. the catch after the fix was that every new place reading chat rows has to remember to hide the emptied ones, except the limit count, which has to keep seeing them. nothing checks that for us.
@vxbe_dev we hit one from the same family last week. deleting a chat also deleted the rows our daily ai limit counts, so you could use up the limit, delete, and start over. now the day's questions get emptied but stay until the nightly cleanup.
@bpecha14 ha, same here. on one change the usual review passes came back clean and a slower, deeper one found 11 real issues. it's too slow and pricey to run every time, so we save it for changes where one rule has to hold in several places at once.
our baby growth calculator was right at exactly 6 or 36 months and wrong on lots of days in between. WHO tables go by day, we looked kids up by month, and round ages were all we tested.
@i_mika_el mikhail, we never gave users a picker. the thing that bit us was on our side: the old fallback was the same model, so when the main one said high demand, the fallback said it too. now the backup is a different company on purpose.
@pinkham pinkham, after a compaction it's working off a summary, and the details it had been careful about were usually what got lost. the agent writes the handoff itself, it's a checklist in its instructions. the only hook runs at session start and prints the open items into the new one.
tested the auto comment filter on one of our sites and it blocked "I felt so stupid for not knowing this earlier". nothing wrong with that comment. the filter still stops swearing and slurs, everything else waits until one of us has read it.
our notes said every AI tool on our parenting site needed a login. i believed it for five weeks. when i tried, six of nine were open to anyone.
the account is prepaid, so a bot wouldn't have sent a bill. it would have drained the balance and shut the AI off. capped it that day.
@ericrbuilds eric, agreed, the quiet ones are worse. our html sanitizer was quietly dropping one block type from our articles, no error anywhere, and it turned out to be invisible on 141 of them.
@samallcock_ sam, we had the reverse of this. our forms had their own error messages, but the browser's built in validation fired first, so visitors got a popup in their own language and our message never showed. tsc, lint, build and review all passed. we only saw it by using the form.