원문 아카이브 | GEO Archive

Google · LighthouseAI 마케팅

/docs/lighthouse/agentic-browsing/webmcp-schema-validity

A valid schema ensures that the AI agent understands the structure of the data it needs to provide. The audit fails if: - A form has a `tooldescription` but is missing the `toolname` attribute. - A form has a `toolname` but is missing the `tooldescription` attribute. - A required form field is missing a `name` attribute. Lighthouse also issues a warning if an optional field has a `name` but is missing a `toolparamdescription` or an associated ` `. 1. Ensure symmetry: Always provide both a name and a description for every tool. 2. Add names to inputs: Verify that every input element within a to

발행일 미상

Google · LighthouseAI 마케팅

/docs/lighthouse/agentic-browsing/forms-missing-declarative-webmcp

While agents can often infer how a form works, providing declarative WebMCP metadata makes interaction more reliable. Lighthouse identifies ` ` elements that don't have both a `toolname` and a `tooldescription`. For now, this audit is informational and does not result in any warnings. Update your HTML forms to include the necessary WebMCP attributes: Sign Up

발행일 미상

Google · LighthouseAI 마케팅

/docs/lighthouse/agentic-browsing/registered-webmcp-tools

Registered tools are the specific capabilities (like "Book a Table" or "Add to Cart") that your website exposes to AI agents. This audit is informational. Lighthouse lists all WebMCP tools registered on the page using the Declarative or Imperative APIs. If no tools are registered, the result list will be empty. Lighthouse issues a warning when more than 40 tools are registered. By including a high excess of tools, you are likely to consume model context tokens, add latency, and increase the risk of confusion for agents as to what tool to use. You can register tools using either the Declarative

발행일 미상

Google · Lighthouse콘텐츠 · SEO

/docs/lighthouse/seo/structured-data

Search engines use structured data to understand what kind of content is on your page. For example, you can tell search engines that your page is an article, a job posting, or an FAQ. Marking up your content with structured data makes it more likely that it will be included in rich search results. For example, content marked up as an article might appear in a list of top stories relevant to something the user searched for. > [!NOTE] > **Note:** The [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview) structured data audit is manual, so it does not affect your Lighthouse SEO scor

발행일 미상

Google · Lighthouse콘텐츠 · SEO

/docs/lighthouse/seo/tap-targets

Tap targets are the areas of a web page that users on touch devices can interact with. Buttons, links, and form elements all have tap targets. Many search engines rank pages based on how mobile-friendly they are. Making sure tap targets are big enough and far enough apart from each other makes your page more mobile-friendly and accessible. [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview) flags pages with tap targets that meet both of these conditions: - The target is smaller than 48 px by 48 px. - At least 25% the target area within 48 px of the center of the target overlaps

발행일 미상

Google · Lighthouse콘텐츠 · SEO

/docs/lighthouse/seo/font-size

> [!WARNING] > **Warning:** This audit has been removed as of Lighthouse 13. For more information see [What's new in Lighthouse 13](https://developer.chrome.com/blog/lighthouse-13-0). Many search engines rank pages based on how mobile-friendly they are. Font sizes smaller than 12 px are often difficult to read on mobile devices and may require users to zoom in to display text at a comfortable reading size. [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview) flags pages with font sizes that are too small to read easily on mobile: ![Lighthouse audit showing page has illegible fon

발행일 미상

Google · Lighthouse콘텐츠 · SEO

/docs/lighthouse/seo/plugins

Search engines often can't index content that relies on browser plugins, such as Java or Flash. That means plugin-based content doesn't show up in search results. Also, most mobile devices don't support plugins, which [creates frustrating experiences for mobile users](https://developers.google.com/search/mobile-sites/mobile-seo/common-mistakes#unplayable-content). [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview) flags pages that use plugins: ![Lighthouse audit showing document uses plugins](https://developer.chrome.com/static/docs/lighthouse/seo/plugins/image/lighthouse-audi

발행일 미상

Google · Lighthouse콘텐츠 · SEO

start of file

The `robots.txt` file tells search engines which of your site's pages they can crawl. An invalid `robots.txt` configuration can cause two types of problems: - It can keep search engines from crawling public pages, causing your content to show up less often in search results. - It can cause search engines to crawl pages you may not want shown in search results. [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview) flags invalid `robots.txt` files: ![Lighthouse audit showing invalid robots.txt](https://developer.chrome.com/static/docs/lighthouse/seo/invalid-robots-txt/image/lightho

발행일 미상

Google · Lighthouse콘텐츠 · SEO

/docs/lighthouse/seo/http-status-code

Servers provide a three-digit [HTTP status code](https://developer.mozilla.org/docs/Web/HTTP/Status) for each resource request they receive. Status codes in the 400s and 500s [indicate that there's an error](https://developer.mozilla.org/docs/Web/HTTP/Status#Client_error_responses) with the requested resource. If a search engine encounters a status code error when it's **crawling** a web page, it may not index that page properly. > [!IMPORTANT] > **Key term:** *Crawling* is how a search engine updates its index of content on the web. [Lighthouse](https://developer.chrome.com/docs/lighthouse/ov

발행일 미상

Perplexity · 공식 API 문서AI 검색

Projects & Billing

> Fetch the complete documentation index at: https://docs.perplexity.ai/llms.txt > Use this file to discover all available pages before exploring further. > Learn how to use the Perplexity API Portal to manage access, usage, billing, and team collaboration. A **Project** is your organization's workspace in the Perplexity API Portal. It allows you to: * **Manage billing** and payment methods for API usage * **Create and control API keys** for accessing the Perplexity API * **Invite team members** and control their permissions (optional) * **Monitor usage and costs** across all your API keys Bef

발행일 미상

원문에서 더 깊이 읽기