How to manage Google Search Console properties across a subdomain fleet

·1 views

A developer running over twenty sites on subdomains of a single domain shares lessons learned from structuring Google Search Console properties. Search Console offers two property types: a domain property covering all subdomains in aggregate, and URL-prefix properties scoping data to individual sites. The author recommends owning both types simultaneously, using prefix properties for per-site monitoring and the domain property for overall coverage. A key pitfall highlighted is the Sitemaps API returning a 403 error that can be mistaken for a missing sitemap, making it essential to track an 'unknown' state separately from a 'missing' one. The author also warns that SC's submitted URL count reflects the last crawl, not live data, and recommends fetching live sitemaps and diffing them against Search Console figures to catch stale indexing.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer builds browser game that scores how well you mimic sounds with your mic

A developer has created Mimic Party Online, a browser-based game where players listen to a short sound cue and attempt to imitate it using their microphone. Each attempt is scored across multiple audio dimensions — including pitch contour, timing, attack, and spectral shape — with labeled breakdowns to help players improve. The game features Quick mode and Survival mode, offering varied challenges and scoring incentives. All audio processing happens locally in the browser at 16 kHz mono PCM, meaning no recordings are sent to external servers. Session state is stored in the browser, allowing players to resume unfinished runs on the same device.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why AI Agents Need Governance Built In, Not Bolted On

A technical analysis published on DEV Community argues that AI agents have evolved from deterministic, rule-following systems into autonomous, goal-oriented entities that require a fundamentally different approach to oversight. The author introduces the concept of AI Governance by Design (AIGD), which embeds ethical, legal, and operational controls into an agent's architecture from the outset rather than treating them as an afterthought. Traditional software testing is deemed insufficient for modern AI agents, since such systems can pass all unit tests yet still produce plausible but operationally dangerous outputs in real-world conditions. The piece outlines three core pillars of agent observability — logging, tracing, and metrics — as tools to monitor not just system uptime but the quality of an agent's reasoning process. The central argument is that agent reliability must be treated as an architectural foundation, not a final validation step before deployment.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

OpenAI Launches Astra with Advanced Cyber Capabilities Under Staged Access Plan

OpenAI officially launched Astra on September 1, 2026, describing it as its most capable model to date. The model has reached what OpenAI calls its 'critical cybersecurity capability threshold' under its Preparedness Framework, triggering additional safeguards. Advanced cybersecurity features will initially be restricted to a small group of testers through a program called Daybreak Blue, rather than being broadly available at launch. OpenAI plans to gradually expand access for defensive use as its safety controls, including misalignment monitoring and scalable oversight, continue to mature. Businesses and security teams are advised to treat Astra as a staged access opportunity rather than a tool immediately ready for production deployment.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How system integration automation can benefit both small and large farm operations

A software developer specializing in agricultural system integration argues that automation in agribusiness goes beyond drones and autonomous tractors, focusing instead on connecting data, decisions, and alerts across farm management tools. Small producers can benefit from low-cost automations such as commodity price alerts via WhatsApp, automated weather warnings using public APIs, and simple digitized harvest and input records to replace scattered spreadsheets. Larger operations with multiple plots or farms gain more from integrations like automatic input reorder triggers, consolidated multi-farm data pipelines, and automated traceability records for export compliance and audits. The author highlights two key challenges unique to rural environments: unreliable internet connectivity, which requires local-first data storage with later sync, and the need to keep human judgment in the loop for consequential agronomic decisions like pesticide application or harvest timing. Open tools such as n8n are recommended for orchestrating these integrations without relying on expensive closed agricultural platforms.

0 comments Read more at DEV Community