add the following information to the comprehensive prompt as you see fit 


additional data =A title link is the title of a search result on Google Search and other properties (for example, Google News) that links to the web page. Google uses a number of different sources to automatically determine the title link, but you can indicate your preferences by following our best practices for influencing title links.

How to make crispy fried eggs

Best practices for influencing title links

Title links are critical to giving users a quick insight into the content of a result and why it's relevant to their query. It's often the primary piece of information people use to decide which result to click, so it's important to use high-quality title text on your web pages.

Make sure every page on your site has a title specified in the <title> element.
Write descriptive and concise text for your <title> elements. Avoid vague descriptors like "Home" for your home page, or "Profile" for a specific person's profile.
Also avoid unnecessarily long or verbose text in your <title> elements. While there's no limit on how long a <title> element can be, the title link is truncated in Google Search results as needed, typically to fit the device width.
Avoid keyword stuffing. It's sometimes helpful to have a few descriptive terms in the <title> element, but there's no reason to have the same words or phrases appear multiple times. Title text like "Foobar, foo bar, foobars, foo bars" doesn't help the user, and this kind of keyword stuffing can make your results look spammy to Google and to users.
Avoid repeated or boilerplate text in <title> elements. It's important to have distinct text that describes the content of the page in the <title> element for each page on your site. Titling every page on a commerce site "Cheap products for sale", for example, makes it impossible for users to distinguish between two pages. Long text in the <title> element that varies by only a single piece of information ("boilerplate" titles) is also bad; for example, a common <title> element for all pages with text like "Band Name - See videos, lyrics, posters, albums, reviews and concerts" contains a lot of uninformative text.

One solution is to dynamically update the <title> element to better reflect the actual content of the page. For example, include the words "video" and "lyrics" only if that particular page contains video or lyrics.

Brand your titles concisely. The <title> element on your site's home page is a reasonable place to include some additional information about your site. For example:
<title>ExampleSocialSite, a place for people to meet and mingle</title>
But displaying that text in the <title> element of every single page on your site will look repetitive if several pages from your site are returned for the same query. In this case, consider including just your site name at the beginning or end of each <title> element, separated from the rest of the text with a delimiter such as a hyphen, colon, or pipe, like this:
<title>ExampleSocialSite: Sign up for a new account.</title>
Make it clear which text is the main title for the page. Google looks at various sources when creating title links, including the main visual title, heading elements, and other large and prominent text, and it can be confusing if multiple headings carry the same visual weight and prominence. Consider ensuring that your main title is distinctive from other text on a page and stands out as being the most prominent on the page (for example, using a larger font, putting the title text in the first visible <h1> element on the page, etc).
Be careful about disallowing search engines from crawling your pages. Using the robots.txt protocol on your site can stop Google from crawling your pages, but it may not always prevent them from being indexed. For example, Google may index your page if we discover it by following a link from someone else's site. If we don't have access to the content on your page, we will rely on off-page content to generate the title link, such as anchor text from other sites. To prevent a URL from being indexed, you can use the noindex rule.
Use the same language and writing system (meaning, the script or alphabet for a given language) as the primary content on your pages. For example, if a page is written in Hindi, make sure to also write the <title> element in Hindi (don't write title text in English or transliterate the title into Latin characters).
Google tries to show a title link that matches the primary language and writing system of a page. If Google determines that a <title> element does not match the writing system or language of the page's primary content, we may choose a different text as the title link.
Avoid including flight price information in <title> elements. Our systems will likely not show price information when generating title links for flight pages. This is because pricing for flights can change so fast (sometimes every few minutes), that what's shown in title links may not correspond to the actual price on the landing page.
How title links in Google Search are created

Google's generation of title links on the Google Search results page is completely automated and takes into account both the content of a page and references to it that appear on the web. The goal of the title link is to best represent and describe each result.

Google Search uses the following sources to automatically determine title links:

Content in <title> elements
Main visual title shown on the page
Heading elements, such as <h1> elements
Content in og:title meta tags
Other content that's large and prominent through the use of style treatments
Other text contained in the page
Anchor text on the page
Text within links that point to the page
WebSite structured data

Keep in mind that Google has to recrawl and reprocess the page to notice updates to these sources, which may take a few days to a few weeks. If you've made changes, you can request that Google recrawl your pages.

While we can't manually change title links for individual sites, we're always working to make them as relevant as possible. You can help improve the quality of the title link that's displayed for your page by following the best practices.

Common issues and how Google manages them
Why the title link in search results might differ from the page's <title> element or main heading: If we've detected an issue on the page, we may try to generate an improved title link from anchors, on-page text, or other sources.

Here are the most common issues we see with title links in search results. To avoid these issues, follow the best practices for influencing title links.

Common issues

Half-empty <title> elements


When part of the title text is missing. For example:

<title>| Site Name</title>

Google Search looks at information in header elements or other large and prominent text on the page to produce a title link:

Product Name | Site Name


Obsolete <title> elements


When the same page is used year-after-year for recurring information, but the <title> element didn't get updated to reflect the latest date. For example:

<title>2020 admissions criteria - University of Awesome</title>

In this example, the page has a large, visible title that says "2021 admissions criteria", and the <title> element wasn't updated to the current date. Google Search may detect this inconsistency and uses the right date from the visible title on the page in the title link:

2021 admissions criteria - University of Awesome


Inaccurate <title> elements


When the <title> elements don't accurately reflect what the page is about. For example, the page could have dynamic content with the following <title> element:

<title>Giant stuffed animals, teddy bears, polar bears - Site Name</title>

Google Search tries to determine if the <title> element isn't accurately showing what a page is about. Google Search might modify the title link to better help users if it determines that the page title doesn't reflect the page content. For example:

Stuffed animals - Site Name


Micro-boilerplate text in <title> elements


When there are repeated boilerplate text in <title> elements for a subset of pages within a site. For example, a television website has multiple pages that share the same <title> element that omits the season numbers, and it's not clear which page is for what season. That produces duplicate <title> elements like this:

<title>My so-called amazing TV show</title>
<title>My so-called amazing TV show</title>
<title>My so-called amazing TV show</title>

Google Search can detect the season number used in large, prominent title text and insert the season number in the title link:

Season 1 - My so-called amazing TV show
Season 2 - My so-called amazing TV show
Season 3 - My so-called amazing TV show


No clear main title


When there's more than one large, prominent heading, and it isn't clear which text is the main title of the page. For example, a page has two or more headings that use the same styling or heading level. If Google Search detects that there are multiple large, prominent headings, it may use the first heading as the text for the title link. Consider ensuring that your main heading is distinctive from other text on a page and stands out as being the most prominent on the page (for example, using a larger font, putting the title text in the first visible <h1> element on the page, etc).



Mismatch of writing system or language used in <title> elements


When the writing system or language of the text in <title> elements doesn't match the writing system or language of the primary text on a page. For example, when a page is in written in Hindi, but the title includes text in English or is transliterated into Latin characters. If Google detects a mismatch, it may generate a title link that better matches the primary content. Consider ensuring that the script and language matches what is most prominent on the page.



Duplication of the site name in the <title> element


In the case of domain-level site names, Google may omit the site name from the title link, if it's repetitive with the site name that's already shown in the search result.

Submitting feedback about title links

If you're seeing your pages appear in the search results with modified title links, check whether your page has one of the issues that Google adjusts for. If not, consider whether the title link in search results is a better fit for the query. To discuss your pages' title links and get feedback about your pages from other site owners, join our Google Search Central Help Community.


Sitelinks are links from the same domain that are clustered together under a text result. Our systems analyze the link structure of your site to find shortcuts that will save users time and allow them to quickly find the information they're looking for.

Pet Paradise: Food, Accessories, and Supplies

Dog supplies

Cat food

Aquariums and accessories

Main search result

Sitelinks

We only show sitelinks for results when we think they'll be useful to the user. If the structure of your site doesn't allow our algorithms to find good sitelinks, or we don't think that the sitelinks for your site are relevant for the user's query, we won't show them.

Sitelinks best practices

At the moment, sitelinks are automated. We're always working to improve our sitelinks algorithms, and we may incorporate site owner input in the future. There are best practices you can follow, however, to improve the quality of your sitelinks.

Make sure that the text you use as your page titles and in your headings is informative, relevant, and compact.
Create a logical site structure that is easy for users to navigate, and make sure you link to your important pages from other relevant pages.
Ensure that your internal links' anchor text is concise and relevant to the page they're pointing to.
Avoid repetitions in your content.

If you need to remove a sitelink, consider removing the page from your site or using noindex.


The following topics describe how you can prevent and monitor abuse on your site.

Topics
Prevent user-generated spam on your site or platform Spammers often take advantage of open comment forms and other user generated content inputs and generate spammy content on an unsuspecting victim site. Learn how to prevent and monitor abuse on your site or platform.
Malware and unwanted software Learn what malware and unwanted software is, guidelines for avoiding distribution of unwanted software, and how to fix problems related to unwanted software.
Prevent a malware infection This article contains tips and pointers for preventing malware infection.
Social Engineering (Phishing and Deceptive Sites) Learn what social engineering is and how to fix it.
Google Safe Browsing Repeat Offenders Policy Google Safe Browsing helps protect users by showing warnings on dangerous sites or dangerous download files.


Spammers often take advantage of open comment forms and other user generated content inputs and generate spammy content on an unsuspecting victim site. Hosting platforms may be similarly open to abuse; spammers may create a large number of sites that violate our spam policies and add little or no value to the web.

Preventing abuse on your platform or site is usually not hard. Even simple deterrents such as an unusual challenge users have to complete before interacting with your property may discourage spammers.

Tell users that you don't allow spam on your service

Publish a clear abuse policy and communicate it to your users, for example during the sign-up process. Furthermore, allow trusted users to report content on your property that they consider spammy.

Identify spammy accounts

Keep a record of signups and other user interactions with your platform, and try to identify typical spam patterns, such as:

Form completion time
Number of requests sent from the same IP address range
User agents used during signup
User names or other form-submitted values chosen during signup

These signals may help you create a user reputation system, which can not only help you engage users, but it can also help identify spammers. Since many comment spammers want their content in search engines, consider adding the noindex robots meta tag on posts that come from new users that don't have any reputation on your platform. Then, after some time, when the user gains reputation, you can allow their content to be indexed. This will greatly demotivate spammers from interacting with your platform.

Since oftentimes spammers are motivated by leaving a link to their site, consider adding a nofollow or ugc rel attribute to all links in untrusted content.

Use manual approval for suspicious user interactions

Manual approval (or moderation) for certain user interactions can decrease spam on your platform considerably by preventing spammers to instantly create content that may be spam. Moderation adds overhead to your daily workflows, however it's a very effective way of fighting spam. Its efficacy is why, for example, comment moderation is a built-in feature in most CMSes.

Use a blocklist to prevent repetitive spamming attempts

Once you find a single spammy profile, make it simple to remove any others. For example, if you see several spammy profiles coming from the same IP address, you can add that IP address to a permanent ban list. For CMSes (for example, WordPress), there are plugins like Akismet that can help, but adding the IP address to your firewall's deny list can be very effective also.

Block automated account creation

In your sign-up form, consider using reCAPTCHAs or similar verification tools to only allow human submissions and prevent automated scripts from generating a lot of sites on your hosting service.

Monitor your service for abuse
Monitor your property for spam signals such as redirects, large numbers of ad sections, certain spammy keywords, and large sections of encoded JavaScript code. The site: search operator or Google Alerts can help detect problems.
Keep an eye on your webserver log files for sudden traffic spikes.
Monitor your property for phishing and malware-infected pages. For example, you can use the Google Safe Browsing API to regularly test URLs from your service.
Come up with a few confidence checks. For example, if you're mainly targeting users in Japan, what are the odds of thousands of user interactions from an Italian IP overnight on your property? A number of tools are available to detect the language of newly created sites—for example language detection libraries or the Google Translate API v2.

Google checks websites to see whether they host software or downloadable executables that negatively affect the user experience. Malware and unwanted software are either downloadable binaries or applications that run on a website and affect site visitors. You can see a list of any suspected files hosted on your site in the Security Issues report.

What is malware?

Malware is any software or mobile application specifically designed to harm a computer, a mobile device, the software it's running, or its users. Malware exhibits malicious behavior that can include installing software without user consent and installing harmful software such as viruses. Website owners sometimes don't realize that their downloadable files are considered malware, so these binaries might be hosted inadvertently.

For more on how Google helps protect users from malicious downloads, see Protecting users from malicious downloads in our Google Online Security Blog.
For our criteria for safe software on the web, see our Unwanted Software Policy.
What is unwanted software?

Unwanted software is an executable file or mobile application that engages in behavior that is deceptive, unexpected, or that negatively affects the user's browsing or computing experience. Examples include software that switches your home page or other browser settings to ones you don't want, or apps that leak private and personal information without proper disclosure.

For more on how Google helps protect users from unwanted software, see That's not the download you're looking for... in our Google Online Security Blog.

In the Security Issues report, "Malware" refers to web-based malware that operates without explicit user action. "Harmful downloads" refers to malware or unwanted software downloads that must be explicitly downloaded by the user.
Fixing the problem

Ensure that your site or application follows the guidelines, then you can request a review in the Security Issues report.

If your mobile application is showing warnings, you can file an appeal.

Guidelines

Be sure that you don't violate the Unwanted Software Policy, and follow the guidelines given here. Though this list isn't comprehensive, these behaviors can cause apps and websites to display warnings to users upon downloading and visiting. You can see a list of any suspected files hosted on your site in the Security Issues report.

Don't misrepresent yourself
Accurately inform users of a software's purpose and intent. Users must be able to download the software intentionally, with accurate knowledge of what will be downloaded, by clicking on an accurate advertisement that clearly informs the user of what will be downloaded. Advertisements leading the user to the download must not be deceptive or inaccurate, such as:
An ad that only contains the words "Download" or "Play" without identifying the software it advertises for.
A "Play" button that leads to a download.
An ad that mimics the look and feel of the publisher's website and pretends to offer content (for example, a movie) but instead leads to unrelated software.
Read about Social Engineering in our Online Security Blog.
Behave as advertised. Make sure your program is clear about its functionality and intentions. If your program collects user data or injects ads into a user's browser, package these behaviors in clear language and don't frame them as insignificant features.
Explicitly and clearly explain to the user what browser and system changes will be made by your software. Allow users to review and approve all significant installation options and changes. Your program's main UI must clearly disclose the binary's components and their primary functionality. The binary must offer an easy way for the user to skip the installation of bundled components. For example, hiding these options or using barely visible text is not good disclosure.
Use endorsements only when authorized. Don't use other companies' logos in an unauthorized way to legitimize or endorse a product. Don't use government logos without authorization.
Don't scare the user. Software must not misrepresent the state of the user's machine to the user, for example by claiming the system is in a critical security state or infected with viruses. Software must not claim to provide a service (for example, "speed up your PC") that it does not or cannot provide. For example, "free" computer cleaners and optimizers must not be advertised as such unless advertised services and components require no payment.
Software guidelines
Use the Google Settings API if your program changes Chrome settings. Any changes to the user's default search settings, startup page, or new tab page must be made using the Chrome Settings Override API, which requires the use of a Chrome extension, as well as compliant extension installation flow.
Allow browser and operating system dialogues to alert the user as intended. Don't suppress alerts to the user from the browser or from the operating system, notably those which inform the user of changes to their browser or OS.
We recommend that you sign your code. While an unsigned binary isn't a reason for flagging your binary as unwanted software, we recommend programs have a valid and verified code signature issued by a code-signing authority that presents verifiable publisher information.
Don't degrade the security and protection measures provided by TLS/SSL connections. An application may not install a root certificate-authority certificate. It may not intercept SSL/TLS connections unless designed for experts to debug or investigate software. For more details, see the related Google Security Blog post.
Protect user data. Software, including mobile apps, must only transmit private user data to servers as it is related to the functionality of the app, and these transmissions must be both disclosed to the user and encrypted.
Do no harm. Your binary must respect and not harm the user's browsing experience. Make sure that your downloadable binaries adhere to the following common policies:
Don't break the browser's reset functionality. Read about the reset browser settings button in Chrome.
Don't bypass or suppress the browser's or operating system's UI control for setting changes. Your program must provide users proper notice and control over settings changes that occur in the browser. Use the Settings API to change Chrome settings (see this Chromium blog post about protecting user settings on Windows with the new Settings API).
Use an extension to change Google Chrome functionality, rather than causing browser behavior change through other programmatic means. For example, your program must not use DLLs (dynamically linked libraries) to inject ads in the browser, must not deploy proxies that intercept traffic, must not use a Layered Service Provider to intercept user actions, or insert new UI into every web page by patching the Chrome binary.
Your product and component descriptions must not scare the user and/or make false, misleading, claims. For example, your product must not make false claims about how the system is in a critical security state or infected with viruses. Programs like registry cleaners must not show alarming messages about the state of a user's computer or device, and claim they can optimize the user's PC.
Make the uninstallation process findable, simple, and non-threatening. You program must have clearly-labeled instructions for returning the browser and/or system to its previous settings. The uninstaller must remove all components and not deter the user from continuing the uninstall process, for example by claiming potential negative effects on the user's system or privacy if the software is uninstalled.
Keep good company. If your software bundles other software components, you are responsible for making sure that none of these components violate any of the recommendations.
Chrome extension guidelines
All extensions need to be disclosed and installed in Chrome to be policy-compliant. Extensions must be hosted in the Chrome Web Store, disabled by default, and compliant with Chrome Web Store policies (including the single-purpose policy). Extensions installed from a program must use the authorized Chrome Extensions installation flow, which will prompt the user to enable them within Chrome. Extensions may not suppress Chrome dialogues alerting the user to settings changes.

Instruct users on how to remove a Chrome Extension. A good user experience is when a user uninstalls a program, everything that was installed along with it gets removed too. The uninstallation flow includes instructions for the user to disable and delete the extension themselves.
If your binary installs a browser add-on or changes default browser settings, it must follow the browser-supported installation flow and API. For example, if the binary installs a Chrome extension, it must be hosted in the Chrome Web Store and adhere to the Chrome Developer Program Policies. Your binary will be identified as malware if it installs a Chrome extension in violation of the Chrome Alternative Extension Distribution Options policy.
Read about silent installs in the Chromium Blog and in our Online Security Blog.
Read how to publish extensions in the Chrome Web Store.
Mobile application guidelines

Inform users of your intent to collect their data. Provide users an opportunity to agree to the collection of their data before you start collecting and sending it from the device, including data about third-party accounts, email, phone number, installed apps, and files on the mobile device. Make sure you securely handle any personal or sensitive user data that you collect, including being transmitted using modern cryptography (for example, over HTTPS). For non-Play apps, you must disclose your data collection to the user in the app. For Google Play apps, disclosure must adhere to Play policy. Don't collect data that goes beyond the published use of your application.

Don't impersonate another brand or app. Don't use improper or unauthorized imagery or design similar to another brand or app in a way that is likely to confuse the user.
Keep all content within the context of the app. Apps must not interfere with other apps and the usability of the device. Apps must not display ads or additional content to the user outside of the context or function of the app itself without getting informed consent from the user and including clear attribution of the ads' source wherever those ads appear.
The app must deliver on promises made to the user. All advertised functionality must be available to the user in the app. Apps may update app content but must not download additional apps without getting informed consent from the user.
Keep behavior transparent. Apps must not uninstall or replace other apps or their shortcuts, unless that is the app's stated purpose. Uninstall must be clear and complete. Apps must not mimic prompts from the device OS or other apps.

Apps distributed through Google Play must comply with the Developer Program Policies and Developer Distribution Agreement, which have additional requirements.

If you're a Search Console user and are having trouble with persistent or unfixable security issues on your site, you can let us know.



The price of freedom from malware is eternal vigilance. This article contains tips and pointers for preventing malware infection. However, it is by no means exhaustive, and Google encourages website owners to conduct more thorough research as well.

Monitoring your site health

Many of the features of Search Console can help you identify potential problems. For example:

Try a search on Google with the site: search operator to see what pages Google has found on your site. It's always a good idea to do this periodically to see whether anyone has snuck unexpected pages or content on your site. If you see unknown pages on your site, or topics that you didn't write, you may have been hacked. If you're not already familiar with the site: search operator, it's a way for you to restrict your search to a specific site. For example, the search site:developers.google.com will return results only from the Google Developers site.
The Security Issues report shows any hacked pages that Google has identified on your site, and instructions on how to fix the problem.
If Google detects malware on your site, you'll see a notification in the message panel in Search Console. To ensure that you're notified quickly, you can have your messages forwarded to your email account.
Security checklist

In addition to monitoring your site regularly, we also recommend the following:

All website owners
Choose good passwords. The Google account guidelines are helpful.
Pick third-party content providers very carefully. Make sure that third-party apps and ads on your site are from trusted and legitimate sources. A trusted and legitimate source provides support and contact information on their website.
Contact your hosting company or publishing platform for support. Most companies have helpful and responsive support groups and/or security pages. If a security page or site has an RSS feed, subscribe to it to make sure you stay up to date.
Keep all of your computers safe. Especially when working on a website, make sure that your local workstation has up-to-date software, is clean from viruses, trojans, or similar malware and has recently updated anti-virus software installed.
Website owners with server access
Check your server configuration. Apache has some security configuration tips on their site and Microsoft has some tech center resources for IIS on theirs. Some of these tips include information on directory permissions, server-side includes, authentication, and encryption.
Make a backup copy of your .htaccess file (or other access control mechanisms depending on your website platform). Use your backup file to recover if the following fails. Be sure to delete the backup file once you are finished.
Stay up-to-date with the latest software updates and patches. There are lots of tools that make building a website easy, but each one adds some risk of being exploited. A common pitfall for many website owners is to install a forum or blog on their website and then forget about it. Much like taking your car in for a tune-up, it's important to make sure you have all the latest updates for any software program you have installed. Make a list of all the software and plug-ins used for your website, and keep track of the version numbers and updates. Even if you're diligent and keep all your website components updated, you may still be vulnerable if your web hoster has not installed the most recent operating system patches. This problem affects not only small sites; there have been warnings on the websites of banks, sports teams, and corporate and government websites.
Keep an eye on your log files. Making this a habit has many great benefits, one of which is added security. For example, unfamiliar URL parameters (like =http: or =//) or spikes in traffic to redirect URLs on your site may indicate that a hacker is exploiting open redirects. Also, bear in mind that hackers often try to alter log files. Take measures to protect these files from attack. For example, you can move these files from their default location, making it harder for hackers to find them.
Check your site for common vulnerabilities. Avoid having directories with open permissions. This is like leaving the front door to your home wide open.

Also check for any XSS (cross-site scripting) and SQL injection vulnerabilities.

Use secure protocols. Google recommends using SSH and SFTP for data transfer, rather than plain text protocols such as telnet or FTP. SSH and SFTP use encryption and are much safer.
Keep up to date on the latest security news. The Google Security Blog provides useful information about online security and safety, as well as pointers to other resources. The government site US-CERT (United States Computer Emergency Readiness Team) provides technical security alerts and tips.

If you're a Search Console user and are having trouble with persistent or unfixable security issues on your site, you can let us know.


Social engineering is content that tricks visitors into doing something dangerous, such as revealing confidential information or downloading software. If Google detects that your website contains social engineering content, the Chrome browser may display a "Deceptive site ahead" warning when visitors view your site. You can check if any pages on your site are suspected of containing social engineering attacks by visiting the Security Issues report in Search Console.

Open the Security Issues Report

What is social engineering?

A social engineering attack is when a web user is tricked into doing something dangerous online.

There are different types of social engineering attacks:

Phishing: The site tricks users into revealing their personal information (for example, passwords, phone numbers, or social security numbers). In this case, the content pretends to act, or looks and feels, like a trusted entity — for example, a browser, operating system, bank, or government.
Deceptive content: The content tries to trick you into doing something you'd only do for a trusted entity — for example, sharing a password, calling tech support, downloading software, or the content contains an ad that falsely claims that device software is out-of-date, prompting users into installing unwanted software.
Insufficiently labeled third-party services: A third-party service is someone that operates a site or service on behalf of another entity. If you (third party) operate a site on behalf of another (first) party without making the relationship clear, that might be flagged as social engineering. For example, if you (first party) run a charity website that uses a donation management website (third party) to handle collections for your site, the donation site must clearly identify that it is a third-party platform acting on behalf of that charity site, or else it could be considered social engineering.

Google Safe Browsing protects web users by warning users before they visit pages that consistently engage in social engineering.

Web pages are considered social engineering when they either:

Pretend to act, or look and feel, like a trusted entity, like your own device or browser, or the website itself, or
Try to trick you into doing something you'd only do for a trusted entity, like sharing a password, or calling a tech support number, or downloading software.
Social engineering in embedded content

Social engineering can also show up in content that is embedded in otherwise benign websites, usually in ads. Embedded social engineering content is a policy violation for the host page.

Sometimes embedded social engineering content will be visible to users on the host page, as shown in the examples. In other cases, the host site does not contain any visible ads, but leads users to social engineering pages via pop-ups, pop-unders, or other types of redirection. In both cases, this type of embedded social engineering content will result in a policy violation for the host page.

But I don't engage in social engineering!

Deceptive social engineering content may be included via resources embedded in the page, such as images, other third-party components, or ads. Such deceptive content may trick site visitors into downloading unwanted software.

Additionally, hackers can take control of innocent sites and use them to host or distribute social engineering content. The hacker could change the content of the site or add additional pages to the site, often with the intent of tricking visitors into parting with personal information such as credit card numbers. You can find out if your site has been identified as a site that hosts or distributes social engineering content by checking the Security Issues report in Search Console.

See our Help for Hacked Sites if you believe that your site has been hacked.

Examples of social engineering violations
Deceptive content examples

Here are some examples of pages that engage in social engineering practices:

Deceptive popup intended to trick the user into installing malware.

Deceptive popup claiming to help the user update their browser

Fake Google login page

Note the deceptive URL. Other phishing sites like this could trick you into giving up other personal information such as credit card information. Phishing sites may look exactly like the real site—so be sure to look at the address bar to check that the URL is correct, and also check to see that the website begins with https://.
Deceptive ad examples

Here are some examples of deceptive content inside embedded ads. These ads appear to be part of the page interface rather than ads.

Deceptive popup claiming that the user's software is out of date.

Deceptive popup claiming to come from the FLV developer

Ads masquerading as page action buttons.

Fixing the problem

If your site is flagged for containing social engineering (deceptive content), ensure that your page doesn't engage in any of the practices, and then follow these steps:

Check in Search Console.
Verify that you own your site in Search Console and that no new, suspicious owners have been added.

Check the Security Issues report to see if your site is listed as containing deceptive content (the reporting term for social engineering). If the report contains sample flagged URLs, visit some of those URLs listed in the report, but use a computer that's not inside the network that is serving your website (clever hackers can disable their attacks if they think the visitor is a website owner).

If the report doesn't contain sample URLs and you're confident your site doesn't contain social engineering (deceptive content), request a security review in the Security Issues report.

Remove deceptive content. Ensure that none of your site's pages contain deceptive content. If you believe Safe Browsing has classified a web page in error, report it.
Check the third-party resources included in your site. Ensure that any ads, images, or other embedded third-party resources on your site's pages are not deceptive.
Note that ad networks may rotate the ads shown on your site's pages. Therefore, you might need to refresh a page a few times before you're able to see any social engineering ads appear.
Some ads may appear differently on mobile devices and desktop computers. You can use the URL Inspection tool to view your site in both mobile and desktop views.
Follow the third-party service guidelines for any third-party services, such as payment services, that you use in your site.
Request a review. After you remove all social engineering content from your site, you can request a security review in the Security Issues report. A review can take several days to complete.
Third-party service guidelines

If you include a third-party service in your site, we recommend that you meet the following conditions in order to avoid being labeled as social engineering:

On every page, the third-party site clearly includes the third-party brand in a way that ensures users understand who is operating the site. For example, by including the third-party brand at the top of the page.
On every page that contains first-party branding, explicitly state the relationship between the first and third party, and provide a link for more information. For example, a statement like this:

This service is hosted by Example.com on behalf of Example.charities.com. More information.

A good usability guideline is whether a user viewing the page in isolation understands which site they are on, and the relationship between the first and third party at all times.

Best practice: If you need a third party to perform a basic support service for your site, a best practice is to use an industry standard third party for that service. For example, to manage user authentication on your site, use OAuth rather than managing authentication yourself.

If you're a Search Console user and are having trouble with persistent or unfixable security issues on your site, you can let us know.



Google provides several Search features and products that help users visually discover information on the web, such as the text result images, Google Discover, and Google Images. While each feature and product looks different, the general recommendations for getting images to appear in them is the same.

You can optimize your images to appear in Google's search results by following these best practices:

Help us discover and index your images
Optimize the image landing pages
Help us discover and index your images

The technical requirements for getting your content in Google's search results applies to images too. Since images are a substantially different format compared to HTML, it means there are additional requirements for getting images indexed; for example, finding the images on your site is different, and the presentation of the images also influences whether an image is indexed at all, and for the right keywords.

Use HTML image elements to embed images

Using standard HTML image elements helps crawlers find and process images. Google can find images in src attribute of <img> element (even when it's a child of other elements, such as the <picture> element). Google doesn't index CSS images.

Good:

<img src="puppy.jpg" alt="A golden retriever puppy" />

Bad:

<div style="background-image:url(puppy.jpg)">A golden retriever puppy</div>
Use an image sitemap

You can provide the URL of images we might not have otherwise discovered by submitting an image sitemap.

Unlike regular sitemaps, you can include URLs from other domains in the <image:loc> elements of the image sitemaps. This allows you to use CDNs (content delivery networks) to host images. If you're using a CDN, we encourage you to verify ownership of the CDN's domain name in Search Console so that we can inform you of any crawl errors that we may find.

Responsive images

Designing responsive web pages leads to better user experience, since people can access them across a plethora of device types. Refer to our guide to responsive images to learn about the best practices for handling images on your website.

Web pages use the <picture> element or the srcset attribute of an img element to specify responsive images. However, some browsers and crawlers do not understand these attributes. We recommend that you always specify a fallback URL via the src attribute.

The srcset attribute allows specifying different versions of the same image, specifically for different screen sizes. For example:

<img srcset="maine-coon-nap-320w.jpg 320w, maine-coon-nap-480w.jpg 480w, maine-coon-nap-800w.jpg 800w" sizes="(max-width: 320px) 280px, (max-width: 480px) 440px, 800px" src="maine-coon-nap-800w.jpg" alt="A watercolor illustration of a maine coon napping leisurely in front of a fireplace">

The <picture> element is a container that is used to group different <source> versions of the same image. It offers a fallback approach so the browser can choose the right image depending on device capabilities, like pixel density and screen size. The picture element also comes in handy for using new image formats with built-in graceful degradation for clients that may not yet support the new formats.

Per section 4.8.1 of the HTML Standard, make sure that you provide an img element as a fallback with a src attribute when using the picture element using the following format:

<picture>
<source type="image/svg+xml" srcset="pyramid.svg">
<source type="image/webp" srcset="pyramid.webp">
<img src="pyramid.png" alt="An 1800s oil painting of The Great Pyramid">
</picture>
Use supported image formats

Google Search supports images referenced in the src attribute of img in the following file formats: BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF. It's also a good idea to have the extension of your filename match with the file type.

You can also inline images as Data URIs. Data URIs provide a way to include a file, such as an image, inline by setting the src attribute of an img element as a Base64-encoded string using the following format:

<img src="data:image/svg+xml;base64,[data]">

While inlining images can reduce HTTP requests, carefully judge when to use them since it can considerably increase the size of the page. For more on this, refer to the section on pros and cons of inlining images on our web.dev page.

Optimize for speed and quality

High-quality photos appeal to users more than blurry, unclear images. Also, sharp images are more appealing to users in the result thumbnail and can increase the likelihood of getting traffic from users. That said, images are often the largest contributor to overall page size, which can make pages slow and expensive to load. Make sure to apply the latest image optimization and responsive image techniques to provide a high quality and fast user experience.

Analyze your site speed with PageSpeed Insights and visit our Why does speed matter? to learn about best practices and techniques to improve website performance.

Optimize the image landing pages

While not immediately obvious, the content and metadata of the pages where an image is embedded can have a great influence on how and where the image may appear in Google's search results.

Check your page title and description

Google Search automatically generates a title link and snippet to best explain each result and how it relates to the user query. This helps users decide whether or not to click on a result. Here are two examples how the title links and snippet might look like on a Google search results page:

We use a number of different sources for this information, including information in the title and meta tags for each page.

You can help us improve the quality of the title link and snippet displayed for your pages by following Google's title and snippet guidelines.

Add structured data

If you include structured data, Google can display your images in certain rich results, including a prominent badge in Google Images, which give users relevant information about your page and can drive better targeted traffic to your site.

Follow the general structured data guidelines as well as any guidelines specific to your structured data type; otherwise your structured data might be ineligible for rich result display in Google Images. In each of these structured data types, the image attribute is a required field to be eligible for a badge and rich result in Google Images. Here are two examples how rich results might look like on Google Images:

Use descriptive filenames, titles, and alt text

Google extracts information about the subject matter of the image from the content of the page, including captions and image titles. Wherever possible, make sure images are placed near relevant text and on pages that are relevant to the image subject matter.

Likewise, the filename can give Google very light clues about the subject matter of the image. When possible, use filenames that are short, but descriptive. For example, my-new-black-kitten.jpg is better than IMG00023.JPG. Avoid using generic filenames like image1.jpg, pic.gif, 1.jpg when possible. If your site has thousands of images, you might want to consider automating the naming of the images. If you localize your images, remember to also translate the filenames, keeping in mind the URL encoding guidelines if you're using non-latin or special characters.

The most important attribute when it comes to providing more metadata for an image is the alt text (text that describes an image), which also improves accessibility for people who can't see images on web pages, including users who use screen readers or have low-bandwidth connections.

Google uses alt text along with computer vision algorithms and the contents of the page to understand the subject matter of the image. Also, alt text in images is useful as anchor text if you decide to use an image as a link.

When writing alt text, focus on creating useful, information-rich content that uses keywords appropriately and is in context of the content of the page. Avoid filling alt attributes with keywords (also known as keyword stuffing) as it results in a negative user experience and may cause your site to be seen as spam.

Bad (missing alt text):

<img src="puppy.jpg"/>

Bad (keyword stuffing):

<img src="puppy.jpg" alt="puppy dog baby dog pup pups puppies doggies pups litter puppies dog retriever labrador wolfhound setter pointer puppy jack russell terrier puppies dog food cheap dogfood puppy food"/>

Better:

<img src="puppy.jpg" alt="puppy"/>

Best:

<img src="puppy.jpg" alt="Dalmatian puppy playing fetch"/>

Also consider the accessibility of your alt text, per W3 guidelines. For the <img> element, you can add the alt attribute of the element, while for inline <svg> elements, you can use the <title> element. For example:

<svg aria-labelledby="svgtitle1"> <title id="svgtitle1">Googlebot wearing an apron and chef hat, struggling to make pancakes on the stovetop</title> </svg>

We recommend testing your content by auditing for accessibility and using a slow network connection emulator.

Opt out of Google Images inline linking

If you choose, you can prevent the full-sized image from appearing in the Google Images search results page by opting out of inline linking in Google Images search results. To opt out of inline linking:

When your image is requested, examine the HTTP referrer header in the request.
If the request is coming from a Google domain, reply with a 200 HTTP status code, or a 204 HTTP status code and no content.

Google will still crawl your page and see the image, but will display a thumbnail image generated at crawl time in search results. This opt-out is possible at any time, and doesn't require re-processing of a website's images. This behavior isn't considered image cloaking and won't result in manual actions.

Alternatively, you can prevent the image from appearing in search results entirely.

Optimize for SafeSearch

SafeSearch is a setting in Google user accounts that specifies whether to show, blur, or block explicit images, videos, and websites in Google Search results. Make sure Google understands the nature of your site so that Google can apply SafeSearch filters to your site if appropriate. Learn more about labeling pages for SafeSearch.



Google uses structured data to understand the content on the page and show that content in a richer appearance in search results, which is called a rich result. This guide focuses on a new carousel rich result that's in beta, which is a list-like rich result that people can scroll horizontally to see more entities from a given site (also known as a host carousel). Each tile in the carousel may have information from your site about the price, rating, and images for entities on the page.

To be eligible for this beta rich result, add ItemList structured data in combination with at least one one of the following supported structured data items:

LocalBusiness and its subtypes, for example:
Restaurant
Hotel
VacationRental
Product
Event

Here's how carousels can look in Google Search when you add ItemList markup in combination with a supported content type:

Feature availability

This feature is in beta and you may see changes in requirements or guidelines, as we develop this feature. If your business is based in EEA, or serves users in EEA, and you would like to learn more and express interest in these new experiences, you can start by filling out the applicable form (for flights queries, use the interest form for flights queries).

This feature is currently only available in European Economic Area (EEA) countries, on both desktop and mobile devices. It's available for travel, local, and shopping queries. For shopping queries, it's being tested first in Germany, France, Czechia, and the UK.

Add structured data

Structured data is a standardized format for providing information about a page and classifying the page content. If you're new to structured data, you can learn more about how structured data works.

Here's an overview of how to add structured data to your site.

Pick a single summary page that contains some information about every entity in the list. For example, a category page that lists the "Top hotels in Paris", with links out to specific detail pages on your site for more information about each hotel. You can mix and match different types of entities (for example, hotels, restaurants), if needed for your scenario. For example, if you have a "Things to do in Switzerland" article that lists both local events and local businesses.
Add the required properties to that summary page. You don't need to add markup to the detail pages in order to be eligible for this beta feature. Based on the format you're using, learn where to insert structured data on the page.
Using a CMS? It may be easier to use a plugin that's integrated into your CMS.
Using JavaScript? Learn how to generate structured data with JavaScript.
Add the required and recommended properties for the specific content type that the carousel is about:
LocalBusiness and its subtypes, for example:
Restaurant
Hotel
VacationRental
Product
Event

Depending on your scenario, you may choose the best type to use. For example, if you have a list of hotels and vacation rentals on your page, use both Hotel and VacationRental types. While it's ideal to use the type that's closest to your scenario, you can choose to use a more generic type (for example, LocalBusiness).

Follow the guidelines.
Validate your code using the Rich Results Test.
Deploy a few pages that include your structured data and use the URL Inspection tool to test how Google sees the page. Be sure that your page is accessible to Google and not blocked by a robots.txt file, the noindex tag, or login requirements. If the page looks okay, you can ask Google to recrawl your URLs.
Note: Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it.
To keep Google informed of future changes, we recommend that you submit a sitemap. You can automate this with the Search Console Sitemap API.
Guidelines

For your page to be eligible for carousel rich results (beta), you must follow the Search Essentials and general structured data guidelines. In addition, the following guidelines apply to carousel rich results (beta):

Use of generic types is allowed. However, to use recommended properties, you must use the respective types. For example, to use amenityFeature, use the LodgingBusiness type.
Use of additional or extra fields is allowed, but may not appear in the rich result.
Your site must have a summary page and multiple detail pages. Currently, this feature isn't designed to support other scenarios, such as an all-in-one page where the "details" are anchor points within the same page.
The markup must be on a summary or category page, which is a list-like page that contains information about at least three entities and then links out to other pages on your site for more information on those entities. While you don't need to add markup to the detail pages, you must include the detail page URLs in your summary page's markup.
Mark up all items that are on the summary or category page. For paginated categories, add an ItemList to each subsequent page and include the entities that are listed on that page. For infinite scroll, focus on marking up the entities that are initially loaded in the viewport.
Examples

The following is a high level structure of the carousel. The order specified in the markup is the order that will be used to order the tiles in the carousel rich result.



<html>
<head>
<title>Top 5 Restaurants in Italy</title>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ItemList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@type": "Restaurant",
"name": "Trattoria Luigi",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$$$",
"servesCuisine": "Italian",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.5,
"reviewCount": 250
},
"url": "https://www.example.com/trattoria-luigi"
}
},
{
"@type": "ListItem",
"position": 2,
"item": {
"@type": "Restaurant",
"name": "La Pergola",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$$$",
"servesCuisine": "Italian",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.9,
"reviewCount": 1150
},
"url": "https://www.example.com/la-pergola"
}
},
{
"@type": "ListItem",
"position": 3,
"item": {
"@type": "Restaurant",
"name": "Pasta e Basta",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$$$",
"servesCuisine": "Italian",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.2,
"reviewCount": 690
},
"url": "https://www.example.com/pasta-e-basta"
}
}
]
}
</script>
</head>
<body>
</body>
</html>

Structured data type definitions

You must include the required properties for your content to be eligible for display as a rich result. You can also include the recommended properties to add more information about your content, which could provide a better user experience.

ItemList

ItemList is the container item that holds all elements in the list. All URLs of the elements in the list must point to different pages on the same domain.

The full definition of ItemList is available at schema.org/ItemList.

Required properties
itemListElement

ListItem

List of items. To specify a list, define an ItemList that contains at least three itemListElement.item elements.


itemListElement.item

Subtype of LocalBusiness, Product, or Event

An individual item in a list. Populate this object with:

The general properties that all carousels must have (image, url, name)
Any other properties required for this data type, as described for your content type:
LocalBusiness and its subtypes
Product
Event

Example: For a hotel, provide priceRange and amenityFeature properties.


itemListElement.position

Integer

The item's position in the carousel. This is a 1-based number.

Common list item properties (LocalBusiness, Product, or Event)

All of the carousel item types have the following properties in common.

Required properties
image

Repeated URL or ImageObject

One or more images of the entity or item (for example, an image of the hotel). Don't include logos in this image property.

Additional image guidelines:

Image URLs must be crawlable and indexable. To check if Google can access your URLs, use the URL Inspection tool.
Images must represent the marked up content.
Images must be in a file format that's supported by Google Images.
For best results, we recommend providing multiple high-resolution images (minimum of 50K pixels when multiplying width and height) with the following aspect ratios: 16x9, 4x3, and 1x1.

For example:

"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
]

name

Text

The string name of the entity or item. For example, the name of a hotel or a vacation listing. The item.name is displayed as the title of an individual item in the carousel. HTML formatting is ignored.


url

URL

The canonical URL of the item detail page (for example, the standalone page for a single hotel or vacation listing that was referenced in the summary page). All URLs in the list must be unique, but live on the same domain (the same domain, or sub or super domain as the summary page).

Anchor links within a summary or category page aren't supported; your site must have standalone detail pages for each item in the list.
Recommended properties
aggregateRating.bestRating

Number

The highest value allowed in this rating system (for example, 5 / 10). If bestRating is omitted, 5 is assumed.


aggregateRating.ratingCount

Number

The total number of ratings for the item on your site.


aggregateRating.ratingValue

Number or Text

A numerical quality rating for the item, either a number, fraction, or percentage (for example, 4, 60%, or 6 / 10). Google understands the scale for fractions and percentages, since the scale is implied in the fraction itself or the percentage. The default scale for numbers is a 5-point scale, where 1 is the lowest value and 5 is the highest value. If another scale is intended, use bestRating and worstRating.

For decimal numbers, use a dot instead of a comma to specify the value (for example 4.4 instead of 4,4). In Microdata and RDFa, you can use content attributes to override the visible content. That way, you can show the user whatever style convention you want, while also satisfying the dot requirement for structured data. For example:

<span itemprop="ratingValue" content="4.4">4,4</span> stars
Additional type-specific properties definitions
LocalBusiness (and subtypes)

In addition to the ListItem properties, Google supports the following LocalBusiness properties (including its subtypes) for carousel rich results Nest these properties under itemListElement.item.

Recommended properties
amenityFeature

LocationFeatureSpecification

For LodgingBusiness only: An amenity feature (for example, a characteristic or service) of the accommodation.

"amenityFeature": {
"@type": "LocationFeatureSpecification",
"name" : "beachAccess",
"value": true
}

priceRange

Text

The relative price range of a business, commonly specified by a normalized number of currency signs. Provide the price range in either of the following formats:

Price level: for example, "$", "$$", "$$$"
Range: for example, "$-$$"

This field must be shorter than 12 characters. If it's longer than 12 characters, Google won't show a price range for the business.


servesCuisine

Text

For restaurants only: The type of cuisine the restaurant serves.

Product

In addition to the ListItem properties, Google supports the following Product properties for carousel rich results. Nest these properties under itemListElement.item.

Recommended properties
offers

Offer or AggregateOffer

A nested Offer or AggregateOffer to sell the product. Include the recommended propeties for either Offer or AggregateOffer (whichever is applicable to your content).

If you're using Offer, including the following properties:

offers.price
offers.priceCurrency

If you're using AggregateOffer, including the following properties:

offers.highPrice
offers.lowPrice
offers.priceCurrency

offers.highPrice

Number

The highest price of all offers available. If you're specifying a single price with price, don't need to include the highPrice and lowPrice properties.


offers.lowPrice

Number

The lowest price of all offers available. If you're specifying a single price with price, don't need to include the highPrice and lowPrice properties.


offers.price

Number

The offer price of a product, or of a price component when attached to PriceSpecification and its subtypes. If you're specifying a price range with lowPrice and highPrice, don't include the price property.


offers.priceCurrency

Text

The currency used to describe the product price, in three-letter ISO 4217 format. If a currency is not provided, Google defaults to USD.

Event

In addition to the ListItem properties, Google supports the following Event properties for carousel rich results. Nest these properties under itemListElement.item.

Recommended properties
offers

Offer or AggregateOffer

A nested Offer or AggregateOffer to sell the event. Include the recommended propeties for either Offer or AggregateOffer (whichever is applicable to your content).

If you're using Offer, including the following properties:

offers.price
offers.priceCurrency

If you're using AggregateOffer, including the following properties:

offers.highPrice
offers.lowPrice
offers.priceCurrency

offers.highPrice

Number

The highest price of all offers available. If you're specifying a single price with price, don't need to include the highPrice and lowPrice properties.


offers.lowPrice

Number

The lowest price of all offers available. If you're specifying a single price with price, don't need to include the highPrice and lowPrice properties.


offers.price

Number

The price for your tickets, including service charges and fees. Don't forget to update it as prices change or tickets sell out. If you're specifying a price range with lowPrice and highPrice, don't include the price property.

If the event is available without payment, fees, or service charges, set the price to 0.

"offers": {
"@type": "Offer",
"price": 0
}

offers.priceCurrency

Text

The currency used to describe the event price, in three-letter ISO 4217 format. If a currency is not provided, Google defaults to USD.

Examples for common scenarios
Restaurant example

Here is an example of a restaurant carousel in JSON-LD.



<html>
<head>
<title>Top 5 Restaurants in Paris</title>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ItemList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@type": "Restaurant",
"name": "Trattoria Luigi",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$$$",
"servesCuisine": "Italian",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.5,
"reviewCount": 250
},
"url": "https://www.example.com/restaurant-location-1"
}
},
{
"@type": "ListItem",
"position": 2,
"item": {
"@type": "Restaurant",
"name": "La Pergola",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$$$",
"servesCuisine": "Italian",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.9,
"reviewCount": 1150
},
"url": "https://www.example.com/restaurant-location-2"
}
},
{
"@type": "ListItem",
"position": 3,
"item": {
"@type": "Restaurant",
"name": "Pasta e Basta",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$$$",
"servesCuisine": "Italian",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.2,
"reviewCount": 690
},
"url": "https://www.example.com/restaurant-location-3"
}
}
]
}
</script>
</head>
<body>
</body>
</html>
Lodging (Hotels and VacationRental) example

Here is an example of a lodging carousel in JSON-LD.



<html>
<head>
<title>Top 5 Hotels in Paris</title>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ItemList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@type": "Hotel",
"name": "Four Seasons Hotel George V, Paris",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$$$$",
"amenityFeature": {
"@type": "LocationFeatureSpecification",
"name" : "internetType",
"value": "Free"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.9,
"reviewCount": 50
},
"url": "https://www.example.com/four-seasons"
}
},
{
"@type": "ListItem",
"position": 2,
"item": {
"@type": "VacationRental",
"name": "Downtown Condo",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$$",
"amenityFeature": {
"@type": "LocationFeatureSpecification",
"name" : "instantBookable",
"value": true
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.7,
"reviewCount": 827
},
"url": "https://www.example.com/downtown-condo"
}
},
{
"@type": "ListItem",
"position": 3,
"item": {
"@type": "Hotel",
"name": "Ritz Paris",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$$$$",
"amenityFeature": {
"@type": "LocationFeatureSpecification",
"name" : "freeBreakfast",
"value": true
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.9,
"reviewCount": 1290
},
"url": "https://www.example.com/ritz-paris"
}
}
]
}
</script>
</head>
<body>
</body>
</html>
Things to do example example

Here is an example of a things to do carousel in JSON-LD.



<html>
<head>
<title>Top 5 Things To Do in Paris</title>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ItemList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@type": "Event",
"name": "Paris Seine River Dinner Cruise",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"offers": {
"@type": "Offer",
"price": 45.00,
"priceCurrency": "EUR"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.2,
"reviewCount": 690
},
"url": "https://www.example.com/event-location1"
}
},
{
"@type": "ListItem",
"position": 2,
"item": {
"@type": "LocalBusiness",
"name": "Notre-Dame Cathedral",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"priceRange": "$",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.8,
"reviewCount": 4220
},
"url": "https://www.example.com/localbusiness-location"
}
},
{
"@type": "ListItem",
"position": 3,
"item": {
"@type": "Event",
"name": "Eiffel Tower With Host Summit Tour",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"offers": {
"@type": "Offer",
"price": 59.00,
"priceCurrency": "EUR"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.9,
"reviewCount": 652
},
"url": "https://www.example.com/event-location2"
}
}
]
}
</script>
</head>
<body>
</body>
</html>

Product example

Here is an example of a product carousel in JSON-LD.



<html>
<head>
<title>Top coats of the season</title>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ItemList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@type": "Product",
"name": "Puffy Coat Series by Goat Coat",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"offers": {
"@type": "AggregateOffer",
"lowPrice": 45.00,
"highPrice": 60.00,
"priceCurrency": "EUR"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.9,
"reviewCount": 50
},
"url": "https://www.example.com/puffy-coats"
}
},
{
"@type": "ListItem",
"position": 2,
"item": {
"@type": "Product",
"name": "Wool Coat Series by Best Coats Around",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"offers": {
"@type": "AggregateOffer",
"lowPrice": 189.00,
"highPrice": 200.00,
"priceCurrency": "EUR"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.7,
"reviewCount": 827
},
"url": "https://www.example.com/wool-coats"
}
},
{
"@type": "ListItem",
"position": 3,
"item": {
"@type": "Product",
"name": "Antartic Coat by Cold Coats",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"offers": {
"@type": "Offer",
"price": 45.00,
"priceCurrency": "EUR"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.9,
"reviewCount": 1290
},
"url": "https://www.example.com/antartic-coat"
}
}
]
}
</script>
</head>
<body>
</body>
</html>

Troubleshooting

If you're having trouble implementing or debugging structured data, here are some resources that may help you.

If you're using a content management system (CMS) or someone else is taking care of your site, ask them to help you. Make sure to forward any Search Console message that details the issue to them.
Google does not guarantee that features that consume structured data will show up in search results. For a list of common reasons why Google may not show your content in a rich result, see the General Structured Data Guidelines.
You might have an error in your structured data. Check the list of structured data errors and the Unparsable structured data report.
If you received a structured data manual action against your page, the structured data on the page will be ignored (although the page can still appear in Google Search results). To fix structured data issues, use the Manual Actions report.
Review the guidelines again to identify if your content isn't compliant with the guidelines. The problem can be caused by either spammy content or spammy markup usage. However, the issue may not be a syntax issue, and so the Rich Results Test won't be able to identify these issues.
Troubleshoot missing rich results / drop in total rich results.
Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it. For general questions about crawling and indexing, check the Google Search crawling and indexing FAQ.
Post a question in the Google Search Central forum.





Comprehensive Prompt for Optimal Meta Generation, Image SEO, Link Optimization, Visual Element Integration, Content Visibility Control, and URL Optimization
Objective:
Generate Meta titles, descriptions, URLs, optimized image attributes, strategically structured links, and content visibility controls for web content that are meticulously optimized to perform exceptionally well in Google Search results (SERP). This includes adhering to Google's Search Essentials, people-first content guidelines, image and link optimization best practices, structured data implementation, content visibility control, URL optimization, and a comprehensive understanding of Google's search algorithms and ranking factors, including optimization for various search result visual elements.

Guidelines:

Technical Requirements:
Meta Elements:
Ensure all Meta elements comply with Google's technical standards for visibility in search results.
Validate that the generated URLs are properly formatted, free of errors, and adhere to SEO best practices.
Ensure that Meta titles and descriptions are free from technical errors such as incorrect character limits or improper formatting.
URL Optimization:
Standards Compliance:
Use URLs as defined by RFC 3986. Reserved characters must be percent-encoded, while unreserved ASCII characters can remain unencoded. Non-ASCII characters should be UTF-8 encoded.
Readability:
Use readable words rather than long ID numbers in your URLs.
Recommended:
Simple, descriptive words:
https://en.wikipedia.org/wiki/Aviation
Localized words if applicable:
https://example.com/lebensmittel/pfefferminz
UTF-8 encoded characters where necessary:
Arabic: https://example.com/%D9%86%D8%B9%D9%86%D8%A7%D8%B9/%D8%A8%D9%82%D8%A7%D9%84%D8%A9
Chinese: https://example.com/%E6%9D%82%E8%B4%A7/%E8%96%84%E8%8D%B7
Umlaut: https://example.com/gem%C3%BCse
Emojis: https://example.com/%F0%9F%A6%99%E2%9C%A8
Not Recommended:
Using non-ASCII characters without encoding:
https://example.com/نعناع
https://example.com/杂货/薄荷
https://example.com/gemüse
https://example.com/🦙✨
Using unreadable, long ID numbers:
https://example.com/index.php?id_sezione=360&sid=3a5ebc944f41daa6f849f730f1
Avoid Fragments:
Do not use fragments to change content as Google generally doesn't support fragment URLs.
Not Recommended:
https://example.com/#/potatoes
Localization and Geotargeting:
For multi-regional sites, use URL structures that facilitate geotargeting.
Recommended:
Country-specific domain: https://example.de
Country-specific subdirectory with gTLD: https://example.com/de/
Word Separation:
Use hyphens (-) to separate words in URLs. Avoid underscores (_) and concatenated words.
Recommended:
https://example.com/summer-clothing/filter?color-profile=dark-grey
Not Recommended:
Underscores: https://example.com/summer_clothing/filter?color_profile=dark_grey
Concatenated words: https://example.com/greendress
URL Parameters:
Use ampersands (&) and equal signs (=) to separate multiple key-value pairs. Avoid using colons (:), brackets ([]), or commas (,).
Recommended:
https://example.com/category?category=dresses&sort=low-to-high&sid=789
Not Recommended:
Colons and brackets: https://example.com/category?[category:dresses][sort:price-low-to-high][sid:789]
Commas: https://example.com/category?category,dresses,,sort,lowtohigh,,sid,789
Common URL Issues and Resolutions:
Overly Complex URLs:
Causes: Additive filtering, dynamic document generation, problematic parameters, calendar issues, broken relative links.
Solutions:
Create a simple and logical URL structure.
Use robots.txt to block problematic URLs.
Avoid session IDs in URLs; use cookies instead.
Standardize URL casing to prevent duplicates.
Shorten URLs by trimming unnecessary parameters.
Add nofollow to infinite calendar links.
Regularly check for and fix broken relative links.
Canonicalization:
Purpose: Select the representative "canonical" URL for duplicate or similar content.
Methods:
Redirects:
Use 301 or 302 redirects to point duplicate URLs to the canonical URL.
Example: Redirecting https://example.com/home and https://home.example.com to https://www.example.com.
rel="canonical" Link Element:
Add a <link rel="canonical"> element in the <head> section of duplicate pages pointing to the canonical URL.
Example:

<link rel="canonical" href="https://example.com/dresses/green-dresses" />
rel="canonical" HTTP Header:
For non-HTML files like PDFs, use the rel="canonical" HTTP header.
Example:

Link: <https://www.example.com/downloads/white-paper.pdf>; rel="canonical"
Sitemap:
Include canonical URLs in your sitemap to suggest preferred versions.
Best Practices:
Use absolute URLs in canonical tags.
Avoid mixed canonical signals (e.g., both robots.txt and noindex).
Do not use fragments in canonical URLs.
Ensure hreflang and canonical URLs are correctly aligned.
Consistently link to canonical URLs within your site.
Avoid:
Using robots.txt for canonicalization.
Using the URL removal tool for canonicalization.
Specifying different canonical URLs using different methods.
Using fragment URLs as canonicals.
Using noindex to manage canonicals within a single site.
Including the HTTP version in sitemaps or hreflang annotations.
Image Optimization:
Use standard <img> elements with descriptive alt text.
Implement responsive images using <picture> or srcset.
Provide descriptive filenames and optimize images for speed and quality.
Use structured data (e.g., ImageObject schema).
Refer to "Image Optimization Best Practices" for detailed steps.
Spam Policies:
Avoid deceptive or manipulative tactics that could lead to lower rankings or removal from search results.
Ensure that the content is original, valuable, and provides a positive user experience.
Adhere to Google's guidelines to prevent actions that may be perceived as spammy, such as keyword stuffing or cloaking.
Key Best Practices:
Content Quality:
Develop helpful, reliable, and people-first content that addresses the needs and interests of the target audience.
Ensure content provides original information, comprehensive coverage, and insightful analysis.
Avoid mass-produced or loosely compiled content; focus on quality and depth.
Eliminate spelling and stylistic issues to maintain professionalism and readability.
E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness):
Experience: Highlight any first-hand experience related to the content topic.
Expertise: Ensure content is written or reviewed by knowledgeable authors or experts in the field.
Authoritativeness: Provide clear authorship information, such as bylines and links to author profiles or the site's About page.
Trustworthiness: Include credible sources, clear sourcing, and evidence of reliability.
Keyword Optimization:
Identify and incorporate relevant keywords that users are likely to search for.
Place primary keywords in prominent locations such as the Meta title, main headings, alt text for images, and within the URL.
Use secondary keywords naturally within the Meta description to support primary keywords.
Understand and align keywords with the intent behind user queries to ensure relevance.
Crawlability:
Ensure all links are crawlable, allowing Google to discover and index other pages on the site effectively.
Implement a logical site structure with clear navigation to facilitate crawling and indexing.
Community Engagement:
Promote the website actively within relevant communities to increase visibility and backlinks.
Encourage user interaction and engagement to enhance the site's authority and trustworthiness.
Multimedia Best Practices:
Follow specific best practices for images, videos, structured data, and JavaScript to enhance content understanding and indexing.
Use descriptive alt text for images and provide transcripts for videos where applicable.
Enhanced Appearance:
Utilize schema markup and other features to improve how the site appears in search results, such as rich snippets.
Implement structured data to provide additional context to search engines about the content.
Content Control:
Use appropriate methods (e.g., robots.txt, meta tags) to manage which content should or shouldn’t appear in search results.
Ensure that noindex tags are correctly applied to prevent sensitive or irrelevant pages from being indexed.
Understanding Google's Search Algorithms and Ranking Factors:
Relevance:
Align content with the user's search intent by understanding the context and purpose behind search queries.
Incorporate synonyms and related terms to capture a broader range of relevant searches.
Ensure that keywords appear naturally within the content, avoiding keyword stuffing.
Quality Signals:
Earn high-quality backlinks from reputable and authoritative websites to enhance content credibility.
Encourage user engagement metrics such as click-through rates (CTR), time on page, and low bounce rates, as these can indirectly influence rankings.
Content Freshness:
Regularly update content to ensure it remains current and relevant, especially for topics where freshness is a key factor (e.g., news, trends).
Implement a content calendar to manage updates and maintain consistent quality.
User Experience (UX):
Optimize page load times to reduce latency and improve overall user satisfaction.
Ensure mobile-friendliness by using responsive design techniques.
Simplify navigation to help users find information quickly and efficiently.
Personalization and Context:
While personalizing content for user intents based on location, history, and settings is essential, ensure that Meta elements remain universally relevant.
Incorporate local keywords if targeting specific geographic areas to enhance local search performance.
Security:
Implement HTTPS to secure user data and enhance trustworthiness, as Google favors secure websites in its rankings.
Regularly perform security audits to protect against vulnerabilities that could negatively impact search rankings.
Page Experience:
Provide a great overall page experience by ensuring fast load times, mobile-friendliness, secure connections (HTTPS), and intuitive navigation.
Optimize Core Web Vitals metrics, including Largest Contentful Paint (LCP), First Input Delay (FID), and Cumulative Layout Shift (CLS), to enhance user experience and potentially improve rankings.
People-First Content Focus:
Create content primarily for users, not solely to manipulate search engine rankings.
Ensure content meets the needs of your existing or intended audience, demonstrating depth of knowledge and satisfying user intent.
Foster trust and loyalty by consistently delivering valuable and reliable information.
Best Practices for Influencing Title Links:
Specify Titles Clearly:
Ensure every page has a unique and descriptive <title> element.
Avoid vague descriptors like "Home" or "Profile" that don't convey specific content information.
Conciseness and Clarity:
Write concise and descriptive <title> elements, typically within 60 characters to prevent truncation.
Avoid unnecessary verbosity and ensure the title accurately reflects the page content.
Avoid Keyword Stuffing:
Use a few descriptive terms naturally without repeating the same keywords or phrases.
Prevent titles from appearing spammy to both Google and users.
Unique Titles for Each Page:
Ensure each page’s <title> element is distinct and accurately describes its unique content.
Avoid boilerplate or repetitive text across multiple pages that makes it difficult to differentiate between them.
Dynamic Title Updates:
Dynamically update the <title> element to reflect the actual content of the page, such as including "video" or "lyrics" only when applicable.
Branding Titles Concisely:
Include your site name in the <title> element of your home page with additional descriptive information.
For other pages, place the site name at the beginning or end of the <title>, separated by a delimiter (e.g., hyphen, colon, pipe).
Clear Main Title:
Ensure the main title of the page is distinctive and prominent, typically within the first visible <h1> element.
Avoid multiple large, prominent headings that can confuse Google about the main title.
Consistent Language and Writing System:
Match the language and writing system of the <title> element with the primary content of the page.
Avoid mixing languages or scripts that can cause Google to generate a different title link.
Avoid Including Price Information in Titles:
Especially for flight pages, refrain from embedding price details in the <title> to prevent discrepancies due to frequent price changes.
Prevent Common Title Link Issues:
Ensure <title> elements are not half-empty, obsolete, inaccurate, duplicated, or mismatched with the page’s language or writing system.
Regularly audit your <title> elements to maintain accuracy and relevance.
Image Optimization Best Practices:
Help Google Discover and Index Your Images:
Use standard HTML <img> elements to embed images, ensuring they are crawlable.
Avoid using CSS background images for important content.
Provide descriptive filenames and alt text for all images.
Use an image sitemap to help Google discover images hosted on CDNs or other domains.
Responsive Images:
Implement responsive images using the <picture> element or srcset attribute with appropriate fallback URLs.
Ensure that the src attribute is always specified as a fallback.
Provide multiple image versions for different screen sizes and resolutions.
Supported Image Formats:
Use supported formats: BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF.
Ensure file extensions match the actual image format.
Optimize for Speed and Quality:
Compress images to reduce file size without compromising quality.
Balance high resolution with fast load times to enhance user experience and search ranking.
Optimize Image Landing Pages:
Ensure that the page containing the image has a unique and descriptive <title> and Meta description.
Place images near relevant text and ensure surrounding content is contextually related.
Use Structured Data:
Implement structured data (e.g., ImageObject schema) to provide additional context about images.
Ensure that images used in structured data meet all requirements, including being annotated with descriptive alt text.
Descriptive Filenames, Titles, and Alt Text:
Use short, descriptive filenames (e.g., dalmatian-puppy-fetch.jpg).
Write informative and concise alt text that accurately describes the image content.
Avoid keyword stuffing in alt text; focus on natural descriptions that aid accessibility.
Accessibility Considerations:
Ensure alt text is clear and descriptive for users relying on screen readers.
Test images with accessibility audit tools to ensure compliance with W3 guidelines.
Opting Out of Google Images Inline Linking:
Implement measures to prevent full-sized images from appearing in Google Images search results if desired.
Use appropriate HTTP status codes based on the referrer to control image display.
Optimize for SafeSearch:
Label pages appropriately to ensure SafeSearch filters are applied where necessary.
Provide clear indicators of the content nature to assist Google in applying SafeSearch settings correctly.
Link Optimization Best Practices:
Make Your Links Crawlable:
Use <a> HTML elements with valid href attributes to create crawlable links.
Recommended Formats (Google can parse):

<a href="https://example.com">
<a href="/products/category/shoes">
<a href="./products/category/shoes">
<a href="/products/category/shoes" onclick="javascript:goTo('shoes')">
<a href="/products/category/shoes" class="pretty">
Not Recommended (Google may still attempt to parse):

<a routerLink="products/category">
<span href="https://example.com">
<a onclick="goto('https://example.com')">
Ensure URLs Resolve Correctly:
Recommended (Google can resolve):

<a href="https://example.com/stuff">
<a href="/products">
<a href="/products.php?id=123">
Not Recommended (Google may still attempt to resolve):

<a href="javascript:goTo('products')">
<a href="javascript:window.location.href='/products'">
Anchor Text Placement:
Use descriptive and relevant anchor text within <a> elements.
Good Example:

<a href="https://example.com/ghost-peppers">ghost peppers</a>
Bad Example (empty link text):

<a href="https://example.com"></a>
For images used as links:

<a href="/add-to-cart.html"><img src="enchiladas-in-shopping-cart.jpg" alt="add enchiladas to your cart"/></a>
Avoid empty alt text and empty link text:

<a href="/add-to-cart.html"><img src="enchiladas-in-shopping-cart.jpg" alt=""/></a>
Write Good Anchor Text:
Good Anchor Text:
Descriptive, concise, and relevant to the linked page.
Example:

<a href="https://example.com/list-of-cheese-types">list of cheese types</a>
Bad Anchor Text:
Too generic, empty, or excessively long.
Example:

<a href="https://example.com">Click here</a>

<a href="https://example.com">Knitted Cow invites local residents of Wisconsin to their grand re-opening by also offering complimentary cow-shaped ice sculptures to the first 20 customers.</a>
Internal Links:
Cross-reference your own content to help users and Google navigate your site.
Ensure every important page has at least one internal link pointing to it.
Use descriptive anchor text that clearly indicates the content of the linked page.
External Links:
Link to reputable external sites to establish trustworthiness and authority.
Use descriptive anchor text that provides context about the linked content.
Use nofollow attributes only when linking to untrusted sources or when necessary (e.g., paid links):

<a href="https://example.com/untrusted-source" rel="nofollow">Untrusted Source</a>
Avoid Excessive Linking:
Maintain a balanced number of internal and external links to avoid overwhelming users and diluting link equity.
Ensure links are relevant and add value to the content.
Understanding How Google Creates Title Links:
Google's title links are generated automatically using various sources, including:
Content within <title> elements.
Main visual titles on the page.
Heading elements (<h1>, <h2>, etc.).
Content within og:title meta tags.
Other large and prominent text through styling.
Anchor text from external links pointing to the page.
WebSite structured data.
Note: Changes to the <title> element require Google to recrawl and reprocess the page, which may take days to weeks.
Submitting Feedback About Title Links:
If title links are modified unexpectedly, check for issues based on the best practices.
Engage with the Google Search Central Help Community to discuss and receive feedback on title link issues.
Controlling Content Visibility in Google Search:
Why Block Content:
Restrict Data: Keep certain data private or accessible only to existing site users.
Hide Low-Value Content: Prevent low-quality or user-generated spam content from affecting site rankings.
Focus on Important Content: Ensure Google prioritizes indexing of high-value and unique content on large sites.
Methods to Block Content:
Remove the Content from Your Site
Applicable: All content types
Description: The best way to ensure content doesn't appear in Google Search is to remove it entirely from your website.
Password-Protect Your Files
Applicable: All content types
Description: Password-protecting ensures only authorized users can access the content, preventing it from being indexed by Google.
noindex Rule
Applicable: All content types
Description: Use the noindex robots meta tag to instruct Google not to index specific pages. The content remains accessible to users via direct links but won't appear in search results.
Example:

<meta name="robots" content="noindex">
Disallow Crawling with robots.txt
Applicable: Images and Videos
Description: Use robots.txt to block Googlebot from accessing specific media files, preventing them from being indexed.
Example:

User-agent: Googlebot-Image
Disallow: /images/private/

User-agent: Googlebot-Video
Disallow: /videos/private/
Opt Out of Specific Google Properties
Applicable: Web Pages
Description: Prevent content from appearing in specific Google services like Google Shopping by adjusting settings or using structured data properties.
Opt Out from Display in the Place Entity Feature in Page Insights
Applicable: Web Pages
Description: For pages with significant place entity content, opt out to prevent these from appearing in Page Insights on Google App browsers in the EEA.
Action: Fill out the Opt-Out Form (replace with actual form link).
Remove Existing Content from Google
Description: If content is already indexed, request its removal using Google's Remove Outdated Content tool or through the Google Search Console.
Action Steps:
Navigate to the Google Search Console Remove URLs tool.
Enter the URL of the content you wish to remove.
Follow the prompts to submit a removal request.
Best Practices for Content Blocking:
Ensure Consistency: If using multiple blocking methods (e.g., robots.txt and noindex), ensure they are consistently applied to avoid conflicting instructions.
Regular Audits: Periodically review your site's content and blocking rules to ensure they align with your current SEO and content strategy.
Monitor Indexing: Use Google Search Console to monitor which pages are indexed and make adjustments to blocking methods as needed.
Things We Believe You Shouldn't Focus On:
Meta Keywords:
Google Search doesn't use the keywords meta tag.
Keyword Stuffing:
Excessively repeating the same words over and over (even in variations) is tiring for users, and keyword stuffing is against Google's spam policies.
Keywords in the Domain Name or URL Path:
When picking the name of your site, do what's best for your business. Users will use this name to find you, so we recommend following general marketing best practices.
From a ranking perspective, the keywords in the name of the domain (or URL path) alone have hardly any effect beyond appearing in breadcrumbs.
The TLD (the domain name ending like ".com" or ".guru") only matters if you're targeting a specific country's users, and even then it's usually a low impact signal.
Minimum or Maximum Content Length:
The length of the content alone doesn't matter for ranking purposes (there's no magical word count target, minimum or maximum, though you probably want to have at least one word).
If you are varying the words (writing naturally to not be repetitive), you have more chances to show up in Search simply because you are using more keywords.
Subdomains versus Subdirectories:
From a business point of view, do whatever makes sense for your business.
Depending on your site's topic or industry, segmenting using subdirectories or subdomains can have different management and SEO implications.
PageRank:
While PageRank uses links and is one of the fundamental algorithms at Google, there's much more to Google Search than just links.
Google employs many ranking signals, and PageRank is just one of those.
Duplicate Content "Penalty":
Having some content that's accessible under multiple URLs is fine; it doesn't cause a manual action.
Copying others' content, however, is a violation and can lead to penalties.
Number and Order of Headings:
Having your headings in semantic order is fantastic for screen readers, but from Google Search perspective, it doesn't matter if you're using them out of order.
There's no magical, ideal amount of headings a given page should have. However, if you think it's too much, then it probably is.
Thinking E-E-A-T is a Ranking Factor:
No, it's not. While E-E-A-T principles are important for content quality and trustworthiness, they are not direct ranking factors.
Enhancing Your SEO Strategy Over Time:
Get Started with Search Console:
Setting up a Search Console account helps you monitor and optimize how your website performs on Google Search.
Learn how to set up your account and what reports to check out first.
Maintain Your Website's SEO Over Time:
Learn more about managing your site's presence in the long term, including more in-depth SEO tasks and scenarios, such as preparing for a site move or managing a multi-lingual site.
Enhance How Your Site Looks in Google Search Results:
Valid structured data on your pages makes your pages eligible for many special features in Google Search results, including review stars, carousels, and more.
Explore the gallery of search result types that your page can be eligible for.
Stay Informed and Ask Questions:
Google Search Central Blog: Get the latest information from the Google Search Central blog, including updates to Google Search, new Search Console features, and more.
Google Search Central on LinkedIn and X (Twitter): Follow for updates on Google Search and resources to help you create a great site.
Google Search Central Help Forum: Post questions about your site's SEO issues and find tips to create high-quality sites from the product forum for website owners.
Google Search Central YouTube Channel: Watch hundreds of helpful videos created for website owners.
Additional Understanding of How Google Search Works:
Stages of Google Search:
Crawling:
Google uses web crawlers (Googlebot) to discover webpages by following links from known pages.
Crawlers respect robots.txt rules and may not crawl pages requiring authentication.
Rendering: Googlebot renders pages using a recent version of Chrome to process JavaScript and dynamically loaded content.
Crawling Issues:
Server problems, network issues, robots.txt disallow rules, inaccessible pages.
Indexing:
After crawling, Google analyzes the content, including text, images, videos, and metadata.
Determines the canonical version in case of duplicate content.
Indexing Issues:
Low-quality content, noindex meta tags, poor site design hindering accessibility.
Serving Search Results:
When a user queries, Google searches the index and ranks relevant pages based on numerous ranking factors.
Factors include query intent, user location, language, device type, and search features.
Serving Issues:
Relevant content but not appearing due to low quality or indexing restrictions.
Visual Elements in Search Results:
Text Result: Includes title link, snippet, attribution, etc.
Rich Result: Enhanced with structured data (e.g., recipes, reviews).
Image Result: Based on images embedded on the page.
Video Result: Based on videos embedded on the page.
Exploration Features: "People also ask" and related searches.
Attribution Details: Favicon, site name, visible URL, domain, breadcrumb.
Optimizing for Different Visual Elements:
Title Links: Follow best practices to influence the generation of accurate and helpful titles.
Snippets: Write compelling meta descriptions to guide both users and Google's snippet generation.
Images and Videos: Optimize using the previously mentioned Image SEO and Video SEO best practices.
Common Reasons for Pages Not Appearing in Search Results:
Content is irrelevant to user queries.
Low-quality content.
noindex rules or other indexing restrictions.
Task:
Using the above guidelines, generate the following Meta elements, image attributes, link strategies, and content visibility controls for the provided web content:

Meta Title:
Maximum of 60 characters.
Incorporate primary keywords naturally.
Clear and descriptive of the page content.
Reflect E-E-A-T by including authoritative terminology if applicable.
Align with user intent and search query relevance.
Follow best practices for influencing title links:
Ensure uniqueness and avoid boilerplate text.
Avoid keyword stuffing and maintain clarity.
Include branding concisely where appropriate.
Meta Description:
Maximum of 160 characters.
Compelling summary that includes secondary keywords.
Encourages click-throughs by highlighting unique value propositions.
Demonstrates trustworthiness and expertise.
Addresses user intent and provides a clear call-to-action if appropriate.
URL:
SEO-friendly structure.
Includes relevant keywords.
Simple, readable, and avoids unnecessary parameters or symbols.
Reflects the content's focus and structure.
Adheres to any specified URL structure preferences (e.g., hyphens vs. underscores).
Image Attributes:
Filename: Use descriptive and concise filenames (e.g., dalmatian-puppy-fetch.jpg).
Alt Text: Provide clear and descriptive alt text (e.g., Dalmatian puppy playing fetch).
Responsive Implementation: Use <picture> or srcset with appropriate fallback.
Structured Data: Implement ImageObject schema where applicable.
Optimization: Ensure images are optimized for speed and quality.
Link Strategies:
Internal Links:
Identify relevant pages within your site to link to using descriptive anchor text.
Ensure every important page is linked from at least one other page on your site.
External Links:
Link to reputable external sources that add value to your content.
Use descriptive anchor text and only apply nofollow when necessary.
Anchor Text:
Ensure anchor text is descriptive, concise, and relevant to the linked content.
Avoid generic phrases like "Click here" or "Read more."
Crawlable Links:
Use <a> elements with valid href attributes for all navigational links.
Avoid using JavaScript or CSS-based links that are not easily crawlable.
Content Visibility Controls:
Choose Appropriate Blocking Methods:
Remove Content: If certain pages or data should not appear in search results, remove them from the website entirely.
Password-Protect Sensitive Areas: Use authentication to restrict access to private content.
Apply noindex Tags: For pages that should remain accessible but not indexed, add the noindex meta tag.

<meta name="robots" content="noindex">
Use robots.txt for Media: Block Googlebot-Image from indexing private images.

User-agent: Googlebot-Image
Disallow: /images/private/
Monitor and Remove Existing Content: Use Google Search Console to request removal of any previously indexed private pages.
Best Practices:
Ensure Consistency: If using multiple blocking methods (e.g., robots.txt and noindex), ensure they are consistently applied to avoid conflicting instructions.
Regular Audits: Periodically review your site's content and blocking rules to ensure they align with your current SEO and content strategy.
Monitor Indexing: Use Google Search Console to monitor which pages are indexed and make adjustments to blocking methods as needed.
Example:

If the content is about "How to Make Crispy Fried Eggs," the generated Meta elements, image attributes, link strategies, and content visibility controls should reflect that focus while demonstrating expertise and trustworthiness.

Meta Title: "How to Make Crispy Fried Eggs | Step-by-Step Guide"
Meta Description: "Learn how to make perfectly crispy fried eggs every time with our easy, step-by-step guide. Delicious and quick breakfast ideas await you!"
URL: https://www.example.com/how-to-make-crispy-fried-eggs
Image Attributes:
Filename: crispy-fried-eggs-step-by-step.jpg
Alt Text: "Step-by-step process of making crispy fried eggs"
Responsive Implementation:

<picture>
  <source type="image/webp" srcset="crispy-fried-eggs-step-by-step.webp">
  <img src="crispy-fried-eggs-step-by-step.jpg" alt="Step-by-step process of making crispy fried eggs">
</picture>
Structured Data:

{
  "@context": "https://schema.org/",
  "@type": "HowTo",
  "name": "How to Make Crispy Fried Eggs",
  "image": {
    "@type": "ImageObject",
    "url": "https://www.example.com/images/crispy-fried-eggs-step-by-step.jpg",
    "height": 800,
    "width": 1200
  },
  "description": "A comprehensive guide on making crispy fried eggs with detailed steps and tips for perfect results."
}
Optimization:
Compressed to reduce file size without compromising quality.
Provided in both JPEG and WebP formats for compatibility and performance.
Link Strategies:
Internal Links:
Link to related recipes or kitchen tips, e.g., <a href="/best-breakfast-recipes">best breakfast recipes</a>.
External Links:
Cite authoritative sources on egg nutrition, e.g., <a href="https://www.healthline.com/nutrition/eggs">health benefits of eggs</a>.
Anchor Text:
Use descriptive anchors such as "crispy fried egg techniques" instead of "click here."
Crawlable Links:
Ensure all navigational links use <a> elements with valid href attributes for optimal crawlability.
Content Visibility Controls:
Remove Unnecessary Content:
Delete any outdated egg recipes from the website to prevent them from appearing in search results.
Apply noindex to Private Pages:
For user-generated content like comments or forums, add noindex tags to prevent indexing.

<meta name="robots" content="noindex">
Password-Protect Sensitive Sections:
Secure sections of the site that contain confidential recipes or user information using authentication measures.
Use robots.txt for Media:
Block Googlebot-Image from indexing private images.

User-agent: Googlebot-Image
Disallow: /images/private/
Monitor and Remove Existing Content:
Use Google Search Console to request removal of any previously indexed private egg recipes.
Next Steps & Additional Information Needed
To ensure the prompt is fully tailored to your project's needs and effectively leverages the provided guidelines, please provide the following additional information:

Content Details:
Topic Description: A detailed overview of the specific topic or subject matter of the web page.
Target Audience: Information about who the content is intended for (e.g., demographics, interests, pain points).
Keyword List:
Primary Keywords: The main keywords you aim to target.
Secondary Keywords: Supporting keywords that complement the primary ones.
Long-Tail Keywords: Specific, longer phrases that target niche search intents related to your content.
Author Information:
Authorship Details: Information about the author(s) or the expertise behind the content. This can include bylines, author bios, or links to authoritative profiles (e.g., LinkedIn, published works).
Brand Guidelines:
Tone of Voice: Specific tone or style preferences (e.g., formal, conversational, authoritative, friendly).
Brand Terminology: Any specific terms or phrases that align with your brand identity.
Brand Values: Key values or messages that should be consistently reflected in the Meta elements.
URL Structure Preferences:
Existing Structures: Preferences or existing patterns for URLs (e.g., use of hyphens vs. underscores, category hierarchies).
Slug Guidelines: Any rules for creating URL slugs related to character length, keyword inclusion, readability, etc.
Canonical URLs: Information about preferred canonical URLs to prevent duplicate content issues.
Examples of Preferred Meta Elements:
Internal Examples: Meta titles and descriptions from your own site that you consider effective or wish to emulate.
Competitor Examples: Meta elements from competitor sites that align with your optimization goals or industry standards.
Additional SEO Considerations:
Localization: If targeting specific geographic regions, include location-based keywords (e.g., "Vegan Recipes for Weight Loss in New York").
Demographics: Tailoring Meta elements to appeal to specific demographic groups (e.g., age, gender, profession).
Call-to-Actions (CTAs): Desired CTAs to include in Meta descriptions to encourage user engagement (e.g., "Learn More," "Get Started Today").
Seasonality: If the content is seasonal, incorporate relevant time-based keywords or phrases.
Content Format and Structure:
Page Layout: Information about how content is structured (e.g., headers, sections, use of bullet points) which can influence keyword placement and Meta elements.
Multimedia Elements: Details about images, videos, or other media included on the page that might influence the Meta elements (e.g., video content may suggest certain keywords or descriptions).
Structured Data: Information about any structured data implemented on the page (e.g., FAQ schema, How-To schema) to enhance the appearance in search results.
Competitor Analysis:
Competitive Keywords: Keywords your competitors are effectively targeting.
Unique Selling Points (USPs): What sets your content apart from competitors, which can be highlighted in Meta descriptions to attract users.
Gap Analysis: Identifying opportunities where competitors may be lacking, allowing you to emphasize strengths in your Meta elements.
Performance Metrics:
Current Rankings: Information about current search rankings for relevant keywords and areas needing improvement.
Traffic Goals: Desired improvements in search traffic, click-through rates (CTR), and engagement metrics.
Conversion Goals: Specific actions you want users to take after clicking through (e.g., sign-ups, purchases).
Regulatory or Compliance Requirements:
Disclaimers: Any necessary legal disclaimers or compliance statements that should be included (e.g., for health-related content).
Content Restrictions: Topics or language that should be avoided to comply with policies or regulations (e.g., avoiding medical advice without certification).
Content Updates:
Frequency: How often the content is updated or refreshed, impacting content freshness signals.
Versioning: Handling of different content versions or updates over time to maintain consistency and relevance in Meta elements.
User Intent Analysis:
Search Intent: Understanding whether the primary intent is informational, navigational, transactional, or commercial investigation to better align Meta elements.
Behavioral Insights: Data or insights on how users interact with similar content, informing the design of Meta elements to better meet user expectations.
Localization and Internationalization:
Language Variations: If the content is available in multiple languages, guidelines for localized Meta elements.
Cultural Sensitivities: Considerations to ensure Meta elements are culturally appropriate and resonate with target audiences in different regions.
Accessibility Considerations:
Inclusive Language: Ensuring that Meta elements use language that is inclusive and accessible to a diverse audience.
Alt Text Guidelines: For images, ensuring that alt text descriptions are clear and descriptive to aid accessibility.
Providing this additional information will enable me to further refine the prompt, ensuring that the generated Meta titles, descriptions, URLs, image attributes, link strategies, and content visibility controls are precisely aligned with your project's objectives, target audience, and Google's best practices. Once you supply these details, we can proceed with generating optimized Meta elements tailored to your specific content.