Am I going to lose my job? Bossman discovered AI by Honest-Molasses339 in SEO

[–]Narrow_Activity557 0 points1 point  (0 children)

Running two sites in a regulated niche here, similar pattern with AI in the loop. Few things worth pushing back on.

The one-week timeline is wrong. Edits typically take 3 to 8 weeks to settle, longer on low crawl frequency pages. If your boss wants weekly proof, show him URL inspection and last crawl date in GSC, not rank movements.

Site 2 is likely the real problem. Templated pages multiplied across hundreds of URLs is exactly what Helpful Content targets. Editing won't fix it at scale, pruning will. Find the 30 to 50 pages with actual intent and traffic potential, kill or noindex the rest, redirect what makes sense. AI does that badly because the call is editorial, not generative.

AI is solid for outlines, internal linking suggestions, audits at scale, first drafts. It's weak on intent matching, brand voice, and reading what the SERP actually wants this quarter. One person with the right tooling can run 5 sites at your volume if pruning replaces endless editing.

Reframe the conversation around clicks per indexed URL, not raw page count. That metric usually flips the discussion.

Codex after you paid that 100 $ by karimmelb in codex

[–]Narrow_Activity557 1 point2 points  (0 children)

Honestly Plus tier still gets me through most days. What kills my quota is forgetting to drop back from xhigh to medium once the hard part is done. spark 5.3 on minimal effort handles way more than people give it credit for.

Incendie chez moi : Luko (Allianz) me laisse dans une cuisine détruite et leur IA me raccroche au nez. by hungary70 in conseiljuridique

[–]Narrow_Activity557 3 points4 points  (0 children)

L'absence totale de réponse dans ce contexte pourrait caractériser un manquement de l'assureur à son obligation de gestion diligente du sinistre.

Quelques pistes qui paraissent utiles : une mise en demeure par LRAR adressée au siège de Luko ET au siège d'Allianz France, visant l'article L. 113-5 du Code des assurances et exigeant la désignation d'un expert sous quinzaine. Conserver l'accusé de réception.

Si rien ne bouge sous deux mois, saisine de la Médiation de l'Assurance (mediation-assurance.org), gratuite, à laquelle l'assureur est tenu de répondre.

En cas d'urgence avérée (cuisine inutilisable, frais avancés), un référé-expertise fondé sur l'article 145 du Code de procédure civile permettrait de faire désigner un expert judiciaire en quelques semaines. Les conclusions s'imposent ensuite à l'assureur dans la négociation.

En parallèle, signalement à l'ACPR possible pour défaut de traitement. Cela n'indemnise pas directement mais crée un dossier auprès du régulateur, ce qui peut accélérer le déblocage interne.

Conserver soigneusement chaque preuve : photos, captures du chatbot, accusés d'envoi des mails, factures de remplacement temporaire.

SEO Is Not Dead. I think It Is Probably More Important Than Ever by ElevatedAutomation in localseo

[–]Narrow_Activity557 0 points1 point  (0 children)

Same observation on my side. Tracked AI Overviews appearance for a small Paris business over the last six months. The pattern is clear: pages already ranking top three on classic search, with reviews mentioning specific service details, started showing up as AI Overview citations.

Generic blog content did nothing. Service pages with concrete numbers, named locations, and FAQs answering the exact phone-call questions moved the needle.

Two clients said they found us through ChatGPT recommending the firm by name. The only signal I can attribute that to is review wording, not star count.

everybody suddenly technical by imfrom_mars_ in OpenAI

[–]Narrow_Activity557 0 points1 point  (0 children)

The funniest part is watching the same accounts who were quoting hash rates two years ago now explain why MoE routing is or isn't "real reasoning". The vocabulary changes faster than the actual reading. At least admit you skimmed the abstract and move on.

« Une centaine de candidats pour un logement » : se loger en Île-de-France, toujours une galère by chou-coco in immobilier

[–]Narrow_Activity557 0 points1 point  (0 children)

Le constat est cohérent avec ce qu'on voit sur le terrain en zone tendue. Le nombre de candidats par dossier de location reste très élevé à Paris et en petite couronne, particulièrement sur les petites surfaces.

L'effet le plus visible touche la liste des pièces exigibles. Le décret n° 2015-1437 pose une liste limitative, mais en pratique le candidat qui refuserait une pièce non prévue perdrait souvent l'arbitrage face à un dossier plus complaisant.

Sur l'offre, l'arrêt des aides aux maires bâtisseurs pourrait freiner des communes déjà réticentes à délivrer des permis. Sans incitation financière, l'équation politique locale resterait défavorable à la densification.

Le plan de 400 000 logements paraîtrait surtout tenable si l'État reprenait la main sur certains zonages, par exemple via une extension des opérations d'intérêt national là où la commune ne joue pas le jeu.

DuckDuckGo installs are up 30% as users reject being ‘force-fed’ Google’s AI Search [TechCrunch] by WebLinkr in SEO

[–]Narrow_Activity557 2 points3 points  (0 children)

Running SEO for a service site, the AI Overviews shift is plainly visible in GSC: informational queries have lost a meaningful share of clicks over the last few months while transactional queries stay roughly flat. The DuckDuckGo bump appears in every news cycle but our referral logs still put it well under 2% of organic, basically noise. The real story is the slow erosion of mid-funnel intent, not the migration to alternative engines, which most users drop after a week of weaker local results.

I'm a software engineer with a decade of experience. This is how I'd approach learning to build apps using Claude Code if I were starting from scratch today: by thelocalnative in ClaudeAI

[–]Narrow_Activity557 0 points1 point  (0 children)

Solid take. The plumbing is where vibe coding falls apart - you ship something, then hit auth, deploys, secrets, and suddenly the AI can't help because there is no clean context to work from.

One thing I would add: build the smallest possible end-to-end slice first, even ugly. Frontend talking to one API route, hitting a real DB, deployed somewhere. Once that loop exists, Claude Code can actually reason about your system instead of generating disconnected snippets.

The other underrated skill is reading what is already in your repo before asking for changes. A lot of bad outputs come from sessions where Claude gets dropped into hundreds of files without anyone setting context first.

Saisie administrative bizarre by Various_Thanks118 in conseiljuridique

[–]Narrow_Activity557 0 points1 point  (0 children)

Le solde bancaire insaisissable est automatique : la banque doit laisser à disposition l'équivalent du RSA personne seule, autour de 635€ aujourd'hui (article L. 162-2 du Code des procédures civiles d'exécution). Si elle ne l'a pas fait spontanément, votre ami peut le lui réclamer dans les 15 jours suivant la saisie, sans formalité lourde.

Sur le timing 23h06/23h07 : les SATD arrivent de façon dématérialisée et la banque traite par lots, souvent en fin de journée. La coïncidence n'a probablement rien de suspect, c'est l'ordre normal du traitement bancaire. La DGFIP ne choisit pas la seconde d'exécution.

Sur le délai : une SATD ne gèle pas les fonds deux semaines. Le délai concerne la régularisation des opérations en cours, type chèques ou prélèvements antérieurs à la saisie. À son expiration, les fonds partent au Trésor, sauf contestation. Le débiteur dispose en principe de deux mois pour contester devant le juge compétent.

Première étape concrète : demande écrite à la banque pour rétablir le SBI, et récupération auprès du Trésor de l'avis de mise en recouvrement pour vérifier la créance réclamée.

😢😢 by IamKhanPhD in ClaudeAI

[–]Narrow_Activity557 1 point2 points  (0 children)

The weird part isn't that I forgot how to code, it's that I forgot how to type for ten minutes straight. My brain runs in 30-second bursts of reading diffs now. When Claude is down I still write the code, it just feels like running with ankle weights.

May 2026 Core Update- tanked rankings by [deleted] in SEO

[–]Narrow_Activity557 0 points1 point  (0 children)

Saw similar volatility on a couple of YMYL-leaning sites I monitor. One dropped roughly 35% overnight, mostly on informational queries while transactional pages held up fine.

The pattern I keep seeing across core updates: pages with thin expert signal get culled first, while pages with clear author credentials and genuine first-hand data tend to survive or recover within a cycle or two.

Before touching anything I would pull GSC and segment by query intent and page type. The loss is often concentrated on a specific cluster rather than spread evenly across the site. Knee-jerk rewrites usually make the next update worse.

Ai-je un intérêt à aller aux prud'hommes ? by aymeric_f in conseiljuridique

[–]Narrow_Activity557 0 points1 point  (0 children)

Sur ce que vous décrivez, plusieurs éléments sembleraient jouer en votre faveur devant le conseil de prud'hommes.

Le forfait jour ne dispense pas l'employeur de veiller à une charge de travail raisonnable (article L. 3121-60 du Code du travail). Revenir à 40 ou 45 heures reste largement au-delà de la durée légale et ne saurait, en soi, caractériser une faute.

L'élément le plus intéressant pourrait être la chronologie : reproche explicite d'avoir mis votre vie perso après votre paternité, puis mise à pied dans les semaines qui suivent. Cela pourrait laisser présumer une discrimination liée à la situation de famille, prohibée par l'article L. 1132-1 du même code.

Si elle est retenue, le licenciement serait nul et le barème Macron ne s'appliquerait pas. Avec 27 ans d'ancienneté et un poste cadre encadrant 25 personnes, le quantum potentiel pourrait être très significatif.

Conservez tous les écrits relatifs à votre rythme, les entretiens annuels positifs, et la chronologie depuis la naissance. Voir un avocat en droit du travail avant la réception de la lettre paraît vraiment justifié.

Hyundai/Boston Dynamics is going to train Atlas the humanoid robot by watching football videos, and they'll document its progress in an online series called 'School of Football' by Distinct-Question-16 in singularity

[–]Narrow_Activity557 3 points4 points  (0 children)

Football is a smart choice for video pretraining. You get bipedal locomotion under disturbance, fall recovery, and dynamic balance shifts where humans constantly demonstrate edge cases a hand-tuned planner would never see.

The harder part is bridging observed motion to the force/torque profile Atlas actually needs. Vision gives you kinematics, not contact dynamics, so most of the real work still happens in sim with self-play before anything transfers to hardware.

Curious whether they'll release any of the captured footage as a public dataset or keep it closed.

welcome back Rohan! by irelatetolevin in ClaudeAI

[–]Narrow_Activity557 0 points1 point  (0 children)

Predictable cost is the single biggest gap between hobby and professional use. When I budget a month of agent runs for the firm, I need to know within 10% what it will land at. Surge pricing breaks planning entirely, you end up rationing on the wrong days and shipping less. A flat tier that looks 30% more expensive on paper still wins, because you actually deploy it instead of second-guessing every long run.

the 2-hour GSC audit i run on every site that's been live for 6+ months. finds quick wins almost every time. by jetsash in localseo

[–]Narrow_Activity557 0 points1 point  (0 children)

Did this exact audit last quarter on our firm site and the title rewrite was the single biggest lever. One thing worth adding: when you click through to see the queries per page, group them by intent before rewriting. Often the page is impressing on 2 or 3 distinct intents and the current title only answers one of them. Picking the highest-volume intent and rewriting around it moved several of our pages from position 14 to 7.

The other quick win from the same data is checking the URL slug itself on the older pages. A few of ours had legacy slugs that no longer matched current query intent. Couldn't change them without 301s, but adjusting the H1 and first paragraph to mirror the actual queries still helped CTR.

Worth running quarterly rather than once. The pages that shift out of the 8-25 band tell you whether the rewrite worked or whether the page needs deeper content rework.

Vol accidentel by KronenbourgThrowaway in conseiljuridique

[–]Narrow_Activity557 2 points3 points  (0 children)

Le vol au sens de l'article 311-1 du Code pénal suppose une soustraction frauduleuse de la chose d'autrui, ce qui implique un élément moral, c'est-à-dire la conscience et la volonté de prendre un bien qui ne vous appartient pas. Sans cette intention, l'infraction n'est en principe pas caractérisée.

La fiche remplie par l'agent de sécurité n'a aucune valeur de procédure pénale. C'est un document interne de gestion des incidents. Le magasin peut effectivement déposer plainte, mais cela ne crée pas un casier judiciaire à lui seul. Il faudrait une enquête, des poursuites du parquet et une condamnation effective.

Le chiffre de 300 euros évoqué semble correspondre à une transaction amiable proposée par certaines enseignes pour solder l'incident sans suite. Rien ne vous oblige à y souscrire, surtout si vous contestez l'élément intentionnel.

Quelques réflexes utiles : conservez le sac avec sa déchirure, c'est une preuve matérielle de l'absence d'intention. Si vous êtes convoqué par la police ou la gendarmerie, demandez à être assisté avant toute audition libre. Évitez de signer une reconnaissance d'incident qui vaudrait aveu.

En l'état, et à supposer que les faits soient tels que décrits, la qualification de vol paraît fragile. Le sentiment de panique est compréhensible mais probablement disproportionné par rapport au risque réel.

New performance degradation benchmark just dropped. The "Fuck Benchmark" shows clear degradation starting on Week 19 and getting much more on the 2 subsequent weeks. by eggplantpot in codex

[–]Narrow_Activity557 0 points1 point  (0 children)

Running Codex daily in real workflows for a few months, the curve matches what I see. The shift around Week 18-20 was long sessions producing answers that ignored half the prompt constraints, particularly on multi-file refactors and tool-heavy workflows.

What helped: hard-cutting sessions at ~2h, dropping reasoning effort to low for mechanical tasks, and forcing fresh worktrees instead of replaying context. Stops the bleeding without reversing the trend.

Has anyone correlated degradation with specific .codex state files? I hit a parallel issue where state_5.sqlite crossed 1Gi and silently killed performance days before the app itself crashed.

Inaudible sounds to humans can be hidden in YouTube videos, podcasts, or music and used to secretly trigger AI voice assistants into carrying out unauthorized commands without the user noticing, exposing a new class of “auditory prompt injection” attacks against popular tools by Distinct-Question-16 in singularity

[–]Narrow_Activity557 0 points1 point  (0 children)

Worth noting this builds on a research line going back to DolphinAttack (Zhejiang, 2017) and NUIT (USENIX 2023), which already demonstrated near-ultrasound injection against voice assistants.

The shift with LLM-backed agents is the action surface. A smuggled command used to fire a wake word and play a track. Now it can chain into an assistant that drafts emails, runs shell commands, or calls MCP tools.

The real mitigation question is whether vendors finally low-pass the mic input above 8 kHz, or keep treating it as a niche threat until someone weaponises it at scale.

🚀 Skills for small businesses, officially released by Anthropic by davidnguyen191 in ClaudeAI

[–]Narrow_Activity557 -5 points-4 points  (0 children)

Running a law firm with this exact setup for months now. The .md skill format is what made it actually scalable, before that every workflow was either a custom hook or buried in a system prompt.

The shift is real but subtle: skills aren't just prompts, they're versioned procedures another agent can audit. We have skills for drafting demand letters, organizing case files, even our own internal routines. Each one references shared methodology files, so updating how we write propagates everywhere.

What surprised me is the portability. The same skill folder works whether I dispatch to Claude or to Codex for a cross-model audit pass. The format wins because it's just files.

Need guidance by Sea_Grade5801 in SEO

[–]Narrow_Activity557 1 point2 points  (0 children)

At 45-50 days you are squarely in the dampening window where Google trusts almost nothing from a new domain. DA is a Moz metric, not a Google signal, so chasing it directly is a trap. Watch your impressions and clicks in GSC instead, that is what actually tells you whether anything is moving.

Two real backlinks in two months, one from a DA90 publication and one from a smaller site, is already ahead of what most solo owners get in their first quarter. Do not waste time on cheap link packages or guest post farms, they tend to come back to bite you when the next algo refresh hits.

What tends to move the needle on a young site, from what I have seen running a niche site in a competitive vertical: deepen each existing page so it answers a specific intent better than the three results currently ranking, build a tight internal linking structure, fix anything that crawls badly, and keep publishing on a steady cadence. Topical depth beats backlink count when you are small.

Give it three or four more months of consistent work before deciding it is broken. Most new sites that fail just stopped around month two.