SShortSingh.
Back to feed

Developer shares personal HTML meta tag reference guide for new projects

0
·1 views

A software developer named Sanudin published a personal reference guide covering essential HTML meta tags used at the start of every new web project. The guide covers foundational settings such as charset, viewport, description, robots, and canonical tags, explaining the practical purpose of each. It also addresses Open Graph and Twitter card tags for social media previews, recommending a 1200×630px image and correct og:type values. The article discusses blocking AI crawlers like GPTBot and ClaudeBot via robots.txt, noting that unofficial tags like noai have inconsistent adoption. Additionally, it explains the use of JSON-LD structured data for entity identity, emphasizing that consistent job titles and sameAs links across profiles help search engines and AI systems recognize a person as a single entity.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

AI Coding Agents Are Widening the Gap Between Strong and Weak Engineers

AI coding agents now allow developers to generate tens of thousands of lines of code in hours, but the requirement to review and understand that code has not changed. Senior engineers who deeply understand system architecture have become more valuable than ever, while developers who rely solely on AI prompts without grasping the underlying logic pose growing risks to production systems. The speed of code generation has far outpaced teams' capacity to meaningfully review what is being merged. This mismatch is creating a structural problem for software teams that adopted AI tools without updating their engineering standards and review processes. The result is a widening divide between engineers who can reason about systems independently and those who cannot explain why their AI-generated code works.

0
ProgrammingDEV Community ·

Google Cloud Guide Pairs Gemini Agent Platform with Cloud Run for Managed AI Inference

Google Cloud offers a managed inference architecture that lets developers deploy AI-powered applications without handling GPUs, model servers, or scaling infrastructure. The approach pairs the Gemini Enterprise Agent Platform, formerly known as Vertex AI, with Cloud Run, splitting responsibilities between orchestration and application logic. Cloud Run hosts custom business logic and client-facing endpoints, while the Agent Platform manages agent state, memory, and model reasoning in a fully managed runtime. Developers use the open-source Agent Development Kit (ADK) to define agent behavior in Python and bind it to Gemini models from the Model Garden. The tiered design allows each layer to scale and fail independently, and ensures clients interact only with Cloud Run rather than directly with the underlying model.

0
ProgrammingDEV Community ·

gomarc brings MARC21 library data processing to Go, outpacing Python's pymarc by up to 11x

A developer has released gomarc v0.1.0, a Go port of the popular Python library pymarc, designed to parse and process MARC21 bibliographic data used in library systems. Benchmarks run on two real catalogue exports totalling over 226,000 records show gomarc completing MARC-8 Unicode parsing up to 11 times faster than its Python counterpart. The library supports reading and writing binary MARC21, MARCXML, and MARC-in-JSON formats, and offers an API familiar to existing pymarc users. Benchmark results were validated for correctness by confirming byte-identical output between both libraries before any performance figures were recorded. The project is at an early v0.1.0 stage, with raw byte decoding and MARC-in-JSON write performance noted as areas still to be optimised.

0
ProgrammingDEV Community ·

How to Build Reliable LLM-Based Content Moderation Using Embeddings and Reranking

A technical architecture for automated content moderation combines semantic search, reranking, and LLM classification to accurately label moderation reports against a defined topic taxonomy. The system retrieves relevant policy passages using embeddings, reranks them to surface the most pertinent evidence, and asks the LLM to classify only against those top passages rather than an entire policy handbook. Every output must conform to a strict JSON schema containing a known topic ID, a confidence score within an allowed range, and cited passage IDs, with invalid or ambiguous responses routed to an explicit unclassified state instead of a silent default. API errors such as HTTP 429 are treated as backpressure with bounded retries, while structurally invalid model responses get one repair attempt before being escalated for human review. The approach prioritizes structured output correctness and audit traceability over model novelty, ensuring reviewers can distinguish retrieval failures from classification failures.