loading
loading
Quick paths into the most useful clusters: indexing, analytics, and security playbooks.
Indexing + GSC (start here)
The fastest paths to fix “discovered/crawled but not indexed” states.
Read →
Discovered - currently not indexed (checklist)
What to fix when Google knows the URL but hasn’t crawled it yet.
Read →
Crawled - currently not indexed (playbook)
What to do when Google crawled the page but decided not to index it.
Read →
Harden CI (GitHub Actions)
Least-privilege permissions, SHA pinning, and PR event pitfalls.
Read →
Web3 wallet safety (start here)
Permit2, signing screens, token approvals, and airdrop safety routines.
Read →
Dependabot policy (safe updates)
Weekly batching + grouping so updates stay reviewable.
Read →
Search by title, description, or tags.
A practical checklist to add minimal-but-sufficient logs for AI apps and automations. Capture the evidence you need for debugging, cost control, and incident response without logging secrets.
A practical checklist to reduce prompt injection and data exfiltration risk in AI apps. Audit your input surfaces, tool permissions, and logging so you can ship with confidence.
A practical CSP rollout plan for Next.js: start in Report-Only, collect violation reports, tighten allowlists, migrate scripts toward nonces/hashes, then enforce with a rollback plan.
A practical checklist for security headers in Next.js. Start with low-breakage headers, add HSTS only when HTTPS is guaranteed, stage CSP in Report-Only, and apply COOP/COEP/CORP only on routes that need cross-origin isolation.
A practical Dependabot operating policy: scope (npm + Actions), weekly batching, grouping, safe defaults for auto-merge, and CI gates that prevent update PRs from becoming incidents.
A practical checklist to harden GitHub Actions as part of your software supply chain. Focus on least-privilege permissions, pinning third-party Actions by SHA, safe handling of fork PRs, and deployment gates.
A practical checklist to reduce npm supply chain risk by treating dependency diffs as security events. Focus on new dependencies, install scripts, lockfile discipline, and incident first moves.
A practical, ops-style authorization checklist to prevent IDOR (broken object-level access control). Focus on where IDs enter, how reads/writes are scoped, consistent deny behavior, and one regression test that prevents reintroducing the bug.
A practical checklist for canonical + hreflang in a multilingual Next.js site. Avoid cross-language canonicals, normalize URLs consistently, and verify alternates via page source, sitemaps, and Search Console.
A practical, security-first checklist to run before connecting a wallet, signing messages, or approving tokens to claim an airdrop. Focus on official entry points, permission intent, and post-claim hygiene.
A practical weekly workflow to collect airdrop leads, verify official sources, track deadlines, and reduce scam exposure — in 30–45 minutes per week.
A practical checklist to move pages from “Crawled - currently not indexed” to indexed. Focus on canonical mistakes, near-duplicate signals, uniqueness upgrades, hubs + related links, and when to stop requesting indexing.
If Search Console shows “Discovered - currently not indexed”, this checklist helps you move pages from discovery to crawl to index by fixing crawl accessibility and increasing internal prioritization—without spamming indexing requests.
AI-assisted development ships fast, and that makes authorization regressions common. This practical guide shows how to detect and fix IDOR (broken object-level authorization) with a repeatable review, tests, and rollout-safe patterns.
Permit2 changed how token approvals are handled in many EVM dApps. Learn what it is, where the risk concentrates, what to check on signing screens, and a practical routine to revoke unused permissions.
A practical checklist for reading wallet signing screens. Learn to identify the action type, counterparty, and scope, and avoid high-risk permissions like Approve, Permit, and SetApprovalForAll.
A practical checklist to set up Google Search Console for a Next.js site on Vercel: choose Domain property, verify with DNS TXT, submit sitemap.xml, and run a minimal post-setup validation to avoid common indexing traps.
A practical prompt template for AI coding that forces decision points into the spec: inputs/outputs, constraints, edge cases, acceptance tests, and phased delivery. Designed for LLM-era teams that need repeatable quality.
Old ERC-20/NFT approvals are a common attack surface. This practical guide explains what approvals mean, when to revoke, and a repeatable audit routine to reduce blast radius.
A practical pre-publish checklist to remove AI-tells in LLM-assisted writing. Focus on reader intent, concrete evidence, decision criteria, and mechanical cleanup so content is scannable and trustworthy.
A practical checklist to build a content site fast (static/Next.js) while preserving resale and migration options (e.g., WordPress later). Focus on portable content, frozen URLs, metadata discipline, and redirect readiness.
A practical playbook for Next.js security updates: decide urgency, upgrade with small diffs, let CI fail fast, verify key flows on preview, deploy with a rollback plan, and rotate secrets when exposure is plausible.
A minimal GA4 + GTM event plan you can ship in a day. Track scroll completion and navigation clicks with stable data attributes, so analytics drives decisions without becoming a maintenance project.
A practical clarifying-questions checklist for AI-assisted development. Turn vague requests into implementable specs by forcing decision points: scope, constraints, failure behavior, acceptance tests, and rollout/ops.
A practical guide to start using Base safely. Follow the first successful path (fund → bridge → verify on explorer), avoid common URL/network mistakes, and build a repeatable checklist.
A practical anti-phishing routine for Web3: control entry points, read wallet permissions before signing, and reduce blast radius after actions. Designed to be repeatable before every connect/sign/claim.
A practical incident response checklist for CVE-2025-66478 in Next.js: confirm exposure, upgrade to patched versions, verify key flows, and rotate secrets when plausible. Written for small teams that need a repeatable process.