'indexing' 검색 결과

When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API. Also use when the user mentions "fix indexing," "not indexed," "Crawled - currently not indexed," "discovered - currently not indexed," "index coverage," "noindex," "noindex tag," "pages not indexed," "why not indexed," "request indexing," or "Google Indexing API." For sitemap, use xml-sitemap.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify indexing problems and coverage issues using Google Search Console URL inspection data. Checks up to 20 pages for indexing status, coverage state, robots.txt state, and last crawl date. Use when user says "index issues", "indexing problems", "not indexed", "indexing coverage", or "why is my page not indexed".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use Google's APIs to review search performance, page speed, indexing status, and organic traffic. Combine real visitor measurements with search and analytics data to identify SEO issues and create reports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing search clicks, impressions, and rankings
• Tracking page experience metrics over 25 weeks
• Checking whether Google has indexed specific URLs

Audit important pages for settings that interfere with search indexing, including noindex directives, HTTP headers, and robots.txt rules. Identify accidental restrictions, suggest configuration fixes, and guide follow-up checks in Google Search Console.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating important pages missing from Google Search
• Checking for leftover staging restrictions after launch
• Reviewing CMS indexing settings for pages and categories

Set up, index, and manage SocratiCode codebase indexing. Use when the user wants to index a project, check infrastructure health, start/stop file watching, configure context artifacts, troubleshoot indexing issues, manage the code graph, or any SocratiCode administrative task. Activates when the user mentions indexing, setting up search, SocratiCode infrastructure, or managing the codebase index.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a reliable Algolia indexing pipeline for full replacements, incremental updates, settings, synonyms, and rules. Use when a source of truth must publish deterministic search state. Trigger with "Algolia indexing workflow", "replace index records", or "sync Algolia".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to implement IndexNow, notify search engines of new/updated URLs, or speed up Bing indexing. Also use when the user mentions "IndexNow," "Bing indexing," "URL notification," "instant indexing," "sitemap IndexNow sync," "share URL list with sitemap," or "IndexNow API." For sitemap SSOT, use xml-sitemap.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fix "content disappears after publishing" bugs caused by REST API indexing lag. Use when: (1) User publishes content but it doesn't appear in their feed/profile, (2) REST API returns stale data immediately after write operations, (3) Async indexing backends (ClickHouse, Elasticsearch, etc.) haven't processed new events, (4) Content shows briefly then vanishes on refresh. Applies to any system with separate write path (WebSocket/direct DB) and read path (REST API with async indexing).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze existing XML sitemaps or generate new ones with GSC indexing cross-reference. Validates format, URLs, and structure against actual indexing status. Use when user says "sitemap", "generate sitemap", "sitemap issues", "XML sitemap", or "sitemap indexing".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Full SEO audit: Google Search Console data + URL Inspection API + PageSpeed Insights API + technical crawl + keyword research + metadata audit + schema markup audit + search intent analysis + Core Web Vitals monitoring. Feeds real GSC data and PageSpeed metrics into AI to surface quick wins, diagnose traffic drops, find content gaps, identify metadata mismatches, detect schema gaps, monitor page performance, and produce an actionable 30-day plan. Use this skill whenever the user asks about SEO, search rankings, organic traffic, Google Search Console, keyword performance, traffic drops, content gaps, search visibility, technical SEO, meta tags, schema markup, structured data, URL indexing, keyword research, indexing issues, page speed, performance, Core Web Vitals, LCP, INP, CLS, or Lighthouse scores. Also trigger on: "why is my traffic down", "what keywords am I ranking for", "improve my rankings", "check my search console", "SEO audit", "analyze my SEO", "technical SEO", "meta tags", "indexing issues", "crawl errors", "content strategy", "keyword cannibalization", "search intent", "schema markup", "structured data", "URL inspection", "page speed", "performance score", "core web vitals", "lighthouse", or any organic search question. If in doubt, trigger. This skill handles everything from quick GSC checks to deep technical audits with performance monitoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds document embedding pipelines with text chunking, embedding generation, indexing, and retrieval optimization. Use when users request "embedding pipeline", "document indexing", "text chunking", "RAG preprocessing", or "semantic indexing".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan and implement a unified AgentDB memory backend for agents. Migrate SQLite and Markdown data, add HNSW indexing for similarity search, and support shared memory and SONA learning patterns while preserving compatibility with existing systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Consolidating separate agent memory systems
• Migrating SQLite and Markdown data to AgentDB
• Finding stored information with similar meaning

Plan and implement a unified AgentDB memory backend for agents. Migrate SQLite and Markdown data, add HNSW indexing for similarity search, and support shared memory and SONA learning patterns while preserving compatibility with existing systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Consolidating separate agent memory systems
• Migrating SQLite and Markdown data to AgentDB
• Finding stored information with similar meaning

Audit a website for problems affecting search visibility, from search engine access and indexing to speed, page titles, content, and links. Receive evidence-based findings and a prioritized action plan, including checks for multilingual and local business sites.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating a drop in search traffic or rankings
• Reviewing page titles and internal links
• Checking multilingual search settings

Audit a site's SEO using its Search Console and GA4 data. Find indexing issues, declining pages, low click rates, and competing pages, then produce specific fixes and a prioritized action list grounded in actual performance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating a drop in organic search traffic
• Checking indexing issues on important pages
• Finding opportunities to improve rankings and click rates

Full SEO audit combining Google Search Console, URL Inspection API, PageSpeed Insights, a technical crawl, keyword research, and metadata, schema, search intent and Core Web Vitals checks. Surfaces quick wins, diagnoses traffic drops and content gaps, and produces an actionable 30-day plan. Use whenever the user asks about SEO, search rankings, organic traffic, Google Search Console, keyword performance, search visibility, technical SEO, URL indexing, or LCP, INP, CLS or Lighthouse scores. Also trigger on: "why is my traffic down", "what keywords am I ranking for", "improve my rankings", "check my search console", "SEO audit", "analyze my SEO", "technical SEO", "meta tags", "indexing issues", "crawl errors", "content strategy", "keyword cannibalization", "search intent", "schema markup", "structured data", "URL inspection", "page speed", "performance score", "core web vitals", "lighthouse", or any organic search question. If in doubt, trigger.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Monitor and optimize Algolia request pressure using observed responses and bounded client behavior. Use when requests return 429, queues grow, or search and indexing compete for capacity. Trigger with "Algolia rate limit", "Algolia 429", or "throttle indexing".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill for general PostgreSQL table design. **Trigger when user asks to:** - Design PostgreSQL tables, schemas, or data models when creating new tables and when modifying existing ones. - Choose data types, constraints, or indexes for PostgreSQL - Create user tables, order tables, reference tables, or JSONB schemas - Understand PostgreSQL best practices for normalization, constraints, or indexing - Design update-heavy, upsert-heavy, or OLTP-style tables **Keywords:** PostgreSQL schema, table design, data types, PRIMARY KEY, FOREIGN KEY, indexes, B-tree, GIN, JSONB, constraints, normalization, identity columns, partitioning, row-level security Comprehensive reference covering data types, indexing strategies, constraints, JSONB patterns, partitioning, and PostgreSQL-specific best practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Standardize video sampling and frame indexing so interval instructions and mask frames stay aligned with a valid key/index scheme.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "google api setup", "real CWV data", "impressions", "clicks", "CTR", "position data", "LCP", "INP", "CLS", "FCP", "TTFB", or "Lighthouse scores".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query writing unless user asks for performance or index help. Prefer indexing as optimization strategy. Use MongoDB MCP when available.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to optimize for mobile-first indexing or fix mobile usability. Also use when the user mentions "mobile-friendly," "mobile-first indexing," "mobile SEO," "responsive design," "mobile adaptation," "mobile viewport," "viewport meta," "touch targets," "font size mobile," "AMP," or "Accelerated Mobile Pages." For viewport meta, use page-metadata.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.