Input: [Then ...] If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning. [If you want to ...]

Output: Get a site added back to Google

Get additional support - Search Console Help


Input: [Then ...] Submit a URL removal request. [If you want to ...]

Output: Get a page or site removed from Google

Get additional support - Search Console Help


Input: [Then ...] Submit a spam report. [If you want to ...]

Output: Report spam

Get additional support - Search Console Help


Input: [Then ...] File a DMCA takedown request. [If you want to ...]

Output: Report a copyright violation or the misuse of your content

Get additional support - Search Console Help


Input: [Then ...] Request a change in crawl rate. [If you want to ...]

Output: Tell Google to crawl your site more slowly

Get additional support - Search Console Help


Input: [Then ...] Submit a SafeSearch issue. [If you want to ...]

Output: Tell Google that your content is mistakenly being filtered by SafeSearch

Get additional support - Search Console Help


Input: [Ad size] 320x50 [Mobile text and display ads*] ✓ [Description]

Output: Also known as the "mobile leaderboard". This format is a mobile-optimised banner. These ads have been shown to work well as a large smartphone ad format, particularly when used at the bottom of a page.


Input: [Ad size] 468x60 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Also known as a "banner". This format can fit into smaller spaces that don't accommodate the 728 x 90 leaderboard. The supply of available display ads for this ad size is generally limited though, which may lead to sub-optimal ad performance.


Input: [Ad size] 234x60 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Also known as a "half banner". This format can fit into small spaces. This size doesn't tend to perform as well as others due to its small size and limited supply of available display ads.


Input: [Ad size] 120x600 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Also known as a "skyscraper", this format can fit into narrower spaces that don't accommodate the 160 x 600 wide skyscraper. The supply of available display ads for this ad size is more limited though, which may lead to sub-optimal ad performance.


Input: [Ad size] 120x240 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Also known as a "vertical banner", this format can fit into small spaces. This size doesn't tend to perform as well as others due to its small size and limited supply of available display ads.


Input: [Ad size] 160x600 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Also known as a "wide skyscraper". Tends to have more ad inventory available from advertisers, which can increase earnings when both text and image ads are enabled. Best if used along sidebars of webpages.


Input: [Ad size] 300x1050 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Also known as a "portrait". A brand-centric format that performs well when placed non-intrusively alongside content on the left or right side of the page. This format integrates well with the content and layout of most websites, and provides advertisers with the ability to create engaging, creative content within this ad unit. While demand from advertisers for larger ad formats is on the rise, the supply of available display ads for this ad size is currently limited.


Input: [Ad size] 970x90 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Sometimes referred to as a "large leaderboard." This ad format expands to 970 x 415 while politely "pushing" all page elements downwards. The first user impression delivers an auto-initiated pushdown experience. All subsequent impressions deliver a user-initiated pushdown which expands via a user click. This size is ideal to showcase High-Definition content such as videos, photos, animations, and applications.


Input: [Ad size] 970x250 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Also known as a "billboard". A brand-centric format that performs well when placed in a premium position on the page, e.g., above the main content of the page. While demand from advertisers for larger ad formats is on the rise, the supply of available display ads for this ad size is currently limited.


Input: [Ad size] 250x250 [Text ads] ✓ [Display ads] ✓ [Mobile text and display ads*] ✓ [Description]

Output: Also known as a "square", this format can fit into smaller spaces that don't accommodate the larger rectangles. The supply of available display ads for this ad size is generally limited though, which may lead to sub-optimal ad performance.


Input: [Ad size] 200x200 [Text ads] ✓ [Display ads] ✓ [Mobile text and display ads*] ✓ [Description]

Output: Also known as a "small square", this format can fit into smaller spaces that don't accommodate the larger rectangles. The supply of available display ads for this ad size is generally limited though, which may lead to sub-optimal ad performance.


Input: [Ad size] 180x150 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Also known as a "small rectangle", this format can fit into small spaces. This size doesn't tend to perform as well as others due to its small size and limited supply of available display ads.


Input: [Ad size] 125x125 [Text ads] ✓ [Display ads] ✓ [Description]

Output: Also known as a "button", this format can fit into small spaces. This size doesn't tend to perform as well as others due to its small size and limited supply of available display ads.


Input: [Then ...] If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning. [If you want to ...]

Output: Get a site added back to Google

Get additional support - Search Console Help


Input: [Then ...] Submit a URL removal request. [If you want to ...]

Output: Get a page or site removed from Google

Get additional support - Search Console Help


Input: [Then ...] Submit a spam report. [If you want to ...]

Output: Report spam

Get additional support - Search Console Help


Input: [Then ...] File a DMCA takedown request. [If you want to ...]

Output: Report a copyright violation or the misuse of your content

Get additional support - Search Console Help


Input: [Then ...] Request a change in crawl rate. [If you want to ...]

Output: Tell Google to crawl your site more slowly

Get additional support - Search Console Help


Input: [Then ...] Submit a SafeSearch issue. [If you want to ...]

Output: Tell Google that your content is mistakenly being filtered by SafeSearch

Get additional support - Search Console Help


Input: Link existing accounts and create new linked accounts Unlink other manager accounts and individual AdWords accounts Invite users to the manager Cancel invitations to the manager account sent by other users Remove a user from the manager account only if the user was originally invited by the administrative user Change access level for manager account users Invite users to linked accounts Give “Standard” or “Read only” access to linked accounts Remove a user from a linked account only if it’s a user they originally invited View, edit, and manage any part of linked accounts and campaigns For users originally invited by the individual AdWords account, a manager account user can change that user’s access to a higher level. To change this type of user from “administrative” access to a lower level, the manager account user can only assign the user a special “managed” lower level access (“Managed - Standard” or “Managed - Read only”). This allows the user to still be able to unlink from the manager account. Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Administrative access

Create an AdWords manager account - AdWords Help


Input: Browse the manager account View, edit, and manage any part of linked accounts and campaigns Sign in and run reports for linked accounts Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Standard access

Create an AdWords manager account - AdWords Help


Input: Browse the manager account Link existing accounts and create new linked accounts Unlink from accounts managed by this manager account View, edit, and manage any part of linked accounts and campaigns Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Managed-Standard access This access level is assigned when a manager account user lowers another user’s access level from “Administrative” to “Standard,” and that user was originally invited to the account by someone else.

Create an AdWords manager account - AdWords Help


Input: Browse the manager account View, sign in, and run reports for linked accounts Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Read only access

Create an AdWords manager account - AdWords Help


Input: Browse the manager account Link existing accounts and create new linked accounts Unlink from accounts managed by this manager account Sign in and run reports for linked accounts Browse linked accounts Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Managed-Read only access This access level is assigned when a manager account user lowers another user’s access level from “Administrative” or “Standard” to “Read only,” and that user was originally invited to the account by someone else.

Create an AdWords manager account - AdWords Help


Input: Receive notification emails for manager account Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Email only access

Create an AdWords manager account - AdWords Help


Input: [Then ...] If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning. [If you want to ...]

Output: Get a site added back to Google

Get additional support - Search Console Help


Input: [Then ...] Submit a URL removal request. [If you want to ...]

Output: Get a page or site removed from Google

Get additional support - Search Console Help


Input: [Then ...] Submit a spam report. [If you want to ...]

Output: Report spam

Get additional support - Search Console Help


Input: [Then ...] File a DMCA takedown request. [If you want to ...]

Output: Report a copyright violation or the misuse of your content

Get additional support - Search Console Help


Input: [Then ...] Request a change in crawl rate. [If you want to ...]

Output: Tell Google to crawl your site more slowly

Get additional support - Search Console Help


Input: [Then ...] Submit a SafeSearch issue. [If you want to ...]

Output: Tell Google that your content is mistakenly being filtered by SafeSearch

Get additional support - Search Console Help


Input: [Then ...] If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning. [If you want to ...]

Output: Get a site added back to Google

Get additional support - Search Console Help


Input: [Then ...] Submit a URL removal request. [If you want to ...]

Output: Get a page or site removed from Google

Get additional support - Search Console Help


Input: [Then ...] Submit a spam report. [If you want to ...]

Output: Report spam

Get additional support - Search Console Help


Input: [Then ...] File a DMCA takedown request. [If you want to ...]

Output: Report a copyright violation or the misuse of your content

Get additional support - Search Console Help


Input: [Then ...] Request a change in crawl rate. [If you want to ...]

Output: Tell Google to crawl your site more slowly

Get additional support - Search Console Help


Input: [Then ...] Submit a SafeSearch issue. [If you want to ...]

Output: Tell Google that your content is mistakenly being filtered by SafeSearch

Get additional support - Search Console Help


Input: [Macro] %a Expands into http://pubads.g.doubleclick.net. [Name]

Output: Host name

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %c Works the same as a double-escaped DoubleClick for Publishers click macro. [Name]

Output: Click

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %e The various expand macros will show the IDs of entities connected with the line item and creative being served and the ad unit to which it's being served. The inventory hierarchy in DoubleClick for Publishers is different from the hierarchy in legacy DART for Publishers, so the way the expand macros identify inventory is also different. The %e expand macros are fully supported in DoubleClick for Publishers, as described below. [Name]

Output: Expand

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %g Works the same as in legacy DART for Publishers. However, the geographic data used for expanding this macro is no longer updated and may be out of date. Values for area codes, postal codes, DMAs, and even some countries may have changed. [Name]

Output: Geo

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %h Only works for creatives trafficked in legacy DART for Publishers. [Name]

Output: File server

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %i Works the same as an unescaped viewed impression macro. However, there is no automatic ad deactivation in DoubleClick for Publishers when the viewed impression macro is not included in the creative code for interstitials. [Name]

Output: Viewed impression

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %k Not supported with Google Publisher Tags. [Name]

Output: Keyword

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %m Not supported. [Name]

Output: Match code

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %n Works the same as the DoubleClick for Publishers cache-busting macro. [Name]

Output: Cache-busting (random number)

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %p Not supported with Google Publisher Tags. [Name]

Output: Pattern match

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %s Expands to the name of the highest-level ad unit above the ad unit where the line item is being served. [Name]

Output: Site name

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %t Works the same as the DoubleClick for Publishers target window macro. [Name]

Output: Target window

DFP macros - DoubleClick for Publishers Help


Input: [Macro] %u Works the same as the escaped DoubleClick for Publishers destination URL macro. [Name]

Output: Destination URL

DFP macros - DoubleClick for Publishers Help


Input: [Code] 300 (Multiple choices) [Description]

Output: The server has several actions available based on the request. The server may choose an action based on the requestor (user agent) or the server may present a list so the requestor can choose an action.


Input: [Code] 301 (Moved permanently) [Description]

Output: The requested page has been permanently moved to a new location. When the server returns this response (as a response to a GET or HEAD request), it automatically forwards the requestor to the new location. You should use this code to let Googlebot know that a page or site has permanently moved to a new location.


Input: [Code] 302 (Moved temporarily) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [Code] 303 (See other location) [Description]

Output: The server returns this code when the requestor should make a separate GET request to a different location to retrieve the response. For all requests other than a HEAD request, the server automatically forwards to the other location.


Input: [Code] 304 (Not modified) [Description]

Output: The requested page hasn't been modified since the last request. When the server returns this response, it doesn't return the contents of the page. You should configure your server to return this response (called the If-Modified-Since HTTP header) when a page hasn't changed since the last time the requestor asked for it. This saves you bandwidth and overhead because your server can tell Googlebot that a page hasn't changed since the last time it was crawled.


Input: [Code] 305 (Use proxy) [Description]

Output: The requestor can only access the requested page using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.


Input: [Code] 307 (Temporary redirect) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [Detail] Geometry type [Description] The type of shape represented in the source data: points lines polygons mixed: multiple shape types unknown: Google Maps Engine was unable to determine the shape [Geometry Type]

Output: All

Vector details - Google Maps Engine Help


Input: [Detail] Feature count [Description] The number of features in the source data, where a feature is a geometry and a set of attributes. Each geometry can consist of multiple points, multiple polygons, or multiple lines. As an example, an archipelago can be one feature with multiple polygons, each of which represents a single island, or multiple features, each containing one of the islands in the archipelago. [Geometry Type]

Output: All

Vector details - Google Maps Engine Help


Input: [Detail] Bad feature count [Description] The number of features that generated errors upon upload. Some of the reasons that features are considered bad are as follows: The feature lacks a geometry. The feature's coordinates are out of bounds. Each coordinate in the dataset must have latitude between +90 and -90 and longitude between +180 and -180. The feature cannot be drawn. For example, the feature is specified to be a polygon but the points that constitute it cannot be drawn to form a polygon. The data with the feature is not encoded as specified. The feature does not have all necessary attributes. [Geometry Type]

Output: All

Vector details - Google Maps Engine Help


Input: [Detail] Vertex count [Description] Each geometry consists of discrete location samples. Vertex count is the sum of such samples. For point data, the sum of all single vertexes. For line data, the sum of all vertex points on all lines. For polygon data, the sum of vertices in the outer and inner loops of all polygons. This value gives some indication of source data complexity. [Geometry Type]

Output: All

Vector details - Google Maps Engine Help


Input: [Detail] Multi-polygon count [Description] If this source data contains multi-polygons, the number present. A multi-polygon is a geometry that consists of multiple polygons, such as a land mass that includes lakes or a lake that includes islands. These inner shapes are listed here as inner lines but can be called inner loops, holes, or cut-outs in other contexts. Note that multiple polygons that constitutes the geometry of a single feature can be treated either as a multi-polygon or as a set of polygons. [Geometry Type]

Output: Polygon

Vector details - Google Maps Engine Help


Input: [Detail] Line count [Description] If this source data contains lines, the number present. [Geometry Type]

Output: Line

Vector details - Google Maps Engine Help


Input: [Detail] Multi-line count [Description] If this source data contains multi-lines, the number present. A multi-line is a geometry that consists of multiple lines, such as a highway whose segments are themselves lines, or a set of all the roads in a county. [Geometry Type]

Output: Line

Vector details - Google Maps Engine Help


Input: [Detail] Point count [Description] If this vector source data contains points, the number present. [Geometry Type]

Output: Point

Vector details - Google Maps Engine Help


Input: [Detail] Bounds [Description] The East/West and North/South coordinates of the box that encloses this feature on a map. Google Maps Engine creates this box by drawing a North/South line at the most easterly and westerly points of the feature, and by drawing an East/West line at the northernmost and southernmost points of the feature. The bounding box contains all of the geometries in your file. [Geometry Type]

Output: All

Vector details - Google Maps Engine Help


Input: [Detail] Altitude [Description] The largest and smallest altitude values in the source data. [Geometry Type]

Output: All

Vector details - Google Maps Engine Help


Input: [Detail] Attribute count [Description] The number of attributes. These attributes are all listed under the Schema header. [Geometry Type]

Output: All

Vector details - Google Maps Engine Help


Input: [Name] Host name Expands into http://pubads.g.doubleclick.net. [Macro]

Output: %a

DFP macros - DoubleClick for Publishers Help


Input: [Name] Click Works the same as a double-escaped DoubleClick for Publishers click macro. [Macro]

Output: %c

DFP macros - DoubleClick for Publishers Help


Input: [Name] Expand The various expand macros will show the IDs of entities connected with the line item and creative being served and the ad unit to which it's being served. The inventory hierarchy in DoubleClick for Publishers is different from the hierarchy in legacy DART for Publishers, so the way the expand macros identify inventory is also different. The %e expand macros are fully supported in DoubleClick for Publishers, as described below. [Macro]

Output: %e

DFP macros - DoubleClick for Publishers Help


Input: [Name] Geo Works the same as in legacy DART for Publishers. However, the geographic data used for expanding this macro is no longer updated and may be out of date. Values for area codes, postal codes, DMAs, and even some countries may have changed. [Macro]

Output: %g

DFP macros - DoubleClick for Publishers Help


Input: [Name] File server Only works for creatives trafficked in legacy DART for Publishers. [Macro]

Output: %h

DFP macros - DoubleClick for Publishers Help


Input: [Name] Viewed impression Works the same as an unescaped viewed impression macro. However, there is no automatic ad deactivation in DoubleClick for Publishers when the viewed impression macro is not included in the creative code for interstitials. [Macro]

Output: %i

DFP macros - DoubleClick for Publishers Help


Input: [Name] Keyword Not supported with Google Publisher Tags. [Macro]

Output: %k

DFP macros - DoubleClick for Publishers Help


Input: [Name] Match code Not supported. [Macro]

Output: %m

DFP macros - DoubleClick for Publishers Help


Input: [Name] Cache-busting (random number) Works the same as the DoubleClick for Publishers cache-busting macro. [Macro]

Output: %n

DFP macros - DoubleClick for Publishers Help


Input: [Name] Pattern match Not supported with Google Publisher Tags. [Macro]

Output: %p

DFP macros - DoubleClick for Publishers Help


Input: [Name] Site name Expands to the name of the highest-level ad unit above the ad unit where the line item is being served. [Macro]

Output: %s

DFP macros - DoubleClick for Publishers Help


Input: [Name] Target window Works the same as the DoubleClick for Publishers target window macro. [Macro]

Output: %t

DFP macros - DoubleClick for Publishers Help


Input: [Name] Destination URL Works the same as the escaped DoubleClick for Publishers destination URL macro. [Macro]

Output: %u

DFP macros - DoubleClick for Publishers Help


Input: [Shortcut] Focus on first element in the conversation list [Keyboard keys]

Output: h then c

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Shortcut] Go into phone mode (same as g then p) [Keyboard keys]

Output: h then p

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Shortcut] Open Hangouts Settings menu [Keyboard keys]

Output: h then m

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Shortcut] Go to Archived Hangouts and focus on first archived Hangout [Keyboard keys]

Output: h then a

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Shortcut] Go to Hangout Invites and focus on first invite [Keyboard keys]

Output: h then i

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Shortcut] Go to Hangouts search box (same as q) [Keyboard keys]

Output: h then q

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Key] aid [Click Command] x [Attribute Inserted]

Output: Ad ID of an ad served

DFP macros - DoubleClick for Publishers Help


Input: [Key] pid [Click Command] x [Attribute Inserted]

Output: Zone ID where an ad is served

DFP macros - DoubleClick for Publishers Help


Input: [Key] sid [Click Command] x [Attribute Inserted]

Output: Site ID where an ad is served

DFP macros - DoubleClick for Publishers Help


Input: [Key] rid [Click Command] x [Attribute Inserted]

Output: Rendering (or creative) ID of a creative delivered

DFP macros - DoubleClick for Publishers Help


Input: [Key] cid [Click Command] x [Attribute Inserted]

Output: Creative ID of a creative delivered

DFP macros - DoubleClick for Publishers Help


Input: [Key] kid [Attribute Inserted]

Output: Key-value ordinal that was matched by the ad servers when choosing an ad to serve

DFP macros - DoubleClick for Publishers Help


Input: [Key] adv [Attribute Inserted]

Output: Advertiser ID of an ad that is served

DFP macros - DoubleClick for Publishers Help


Input: [Key] env [Attribute Inserted]

Output: Environment character, which specifies the type of ad slot (/, f, i, j, l, or x) / - standard image-based ad f - in a frame i - in an iframe j - using JavaScript l - in a layer x - using streaming technologies.

DFP macros - DoubleClick for Publishers Help


Input: [Key] rv [Attribute Inserted]

Output: Rendering version, which is the version of a creative that is delivered

DFP macros - DoubleClick for Publishers Help


Input: [Key] buy [Click Command] x [Attribute Inserted]

Output: Buy or order ID of an ad served

DFP macros - DoubleClick for Publishers Help


Input: [Example URL] http://books.google.com/books?vid=OCLC17546826&printsec=frontcover [Page]

Output: Front cover

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?vid=OCLC17546826&printsec=titlepage [Page]

Output: Title page

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?vid=LCCN88005048&printsec=copyright [Page]

Output: Copyright page

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?id=05R7kYOKD0cC&printsec=toc [Page]

Output: Table of contents

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?vid=ISBN0521349931&printsec=index [Page]

Output: Index

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?vid=OCLC17546826&printsec=backcover [Page]

Output: Back cover

Linking to individual titles on Google Books - Books Help


Input: [If you want to ...] Get a site added back to Google [Then ...]

Output: If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning.

Get additional support - Search Console Help


Input: [If you want to ...] Get a page or site removed from Google [Then ...]

Output: Submit a URL removal request.

Get additional support - Search Console Help


Input: [If you want to ...] Report spam [Then ...]

Output: Submit a spam report.

Get additional support - Search Console Help


Input: [If you want to ...] Report a copyright violation or the misuse of your content [Then ...]

Output: File a DMCA takedown request.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google to crawl your site more slowly [Then ...]

Output: Request a change in crawl rate.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google that your content is mistakenly being filtered by SafeSearch [Then ...]

Output: Submit a SafeSearch issue.

Get additional support - Search Console Help


Input: Administrative access Link existing accounts and create new linked accounts Unlink other manager accounts and individual AdWords accounts Invite users to the manager Cancel invitations to the manager account sent by other users Remove a user from the manager account only if the user was originally invited by the administrative user Change access level for manager account users

Output: Invite users to linked accounts Give “Standard” or “Read only” access to linked accounts Remove a user from a linked account only if it’s a user they originally invited View, edit, and manage any part of linked accounts and campaigns For users originally invited by the individual AdWords account, a manager account user can change that user’s access to a higher level. To change this type of user from “administrative” access to a lower level, the manager account user can only assign the user a special “managed” lower level access (“Managed - Standard” or “Managed - Read only”). This allows the user to still be able to unlink from the manager account. Receive notification emails for linked accounts Receive emailed reports, if added to email list

Create an AdWords manager account - AdWords Help

What the manager account user can do in linked managed accounts


Input: Standard access Browse the manager account

Output: View, edit, and manage any part of linked accounts and campaigns Sign in and run reports for linked accounts Receive notification emails for linked accounts Receive emailed reports, if added to email list

Create an AdWords manager account - AdWords Help

What the manager account user can do in linked managed accounts


Input: Managed-Standard access This access level is assigned when a manager account user lowers another user’s access level from “Administrative” to “Standard,” and that user was originally invited to the account by someone else. Browse the manager account Link existing accounts and create new linked accounts Unlink from accounts managed by this manager account

Output: View, edit, and manage any part of linked accounts and campaigns Receive notification emails for linked accounts Receive emailed reports, if added to email list

Create an AdWords manager account - AdWords Help

What the manager account user can do in linked managed accounts


Input: Read only access Browse the manager account

Output: View, sign in, and run reports for linked accounts Receive notification emails for linked accounts Receive emailed reports, if added to email list

Create an AdWords manager account - AdWords Help

What the manager account user can do in linked managed accounts


Input: Managed-Read only access This access level is assigned when a manager account user lowers another user’s access level from “Administrative” or “Standard” to “Read only,” and that user was originally invited to the account by someone else. Browse the manager account Link existing accounts and create new linked accounts Unlink from accounts managed by this manager account

Output: Sign in and run reports for linked accounts Browse linked accounts Receive notification emails for linked accounts Receive emailed reports, if added to email list

Create an AdWords manager account - AdWords Help

What the manager account user can do in linked managed accounts


Input: Email only access Receive notification emails for manager account

Output: Receive notification emails for linked accounts Receive emailed reports, if added to email list

Create an AdWords manager account - AdWords Help

What the manager account user can do in linked managed accounts


Input: [Description] Delivery for these line items has slowed to ensure that they don’t overdeliver. Ensure that the flight dates, quantity goals, and frequency caps are correct.

Output: Ahead of schedule

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] These line items were targeted to times of day different than the ones targeted by the ad unit. Ensure the dayparting settings are correct.

Output: Current time outside of dayparting window

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] These line items have stopped serving because they reached their quantity goals or their end date has passed. If you need to restart the line item, you must copy it and give it new start and end dates.

Output: Delivery goals reached

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] These line items have hit the limit for how many times they can be delivered to the same user within the established time period. Ensure the frequency capping settings are correct.

Output: Frequency cap reached

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] The flight dates of these line items don’t match the targeting settings of the ad unit. Ensure that the flight dates of the line item you want to deliver match the flight dates of the ad unit.

Output: Incompatible start or end date

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] There aren't enough ad slots on the page to accommodate all of the creatives the line items are set to deliver. Ensure the number of creatives is equal to or less than the number of ad slots on the page.

Output: Limited by number of ads per page

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] The line items haven't started running either because their flight dates and times haven't started yet or the line items haven't been activated. See Line item isn't delivering ads to troubleshoot the problem.

Output: Line item not active

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] The line items need creatives, are paused or cancelled, or their inventory was released. Add creatives, check why they were paused or cancelled, or check why their inventory was released.

Output: Line item not ready

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] The line items don't have creatives that match the sizes of the ad slots on the page. Add at least one creative that has the same size as an ad unit on the page.

Output: No active right-sized creative associated

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] The line items aren't targeting any of the ad units on the page. Check the line item's inventory targeting and ensure it's targeting at least one of the ad units on the page.

Output: Not targeting any active ad units

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] The line items aren't targeting any placements assigned to this web page. Check the line item's inventory targeting and ensure it's targeting at least one of the placements assigned to this web page.

Output: Not targeting any active placements

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] The order that contains the line items must be approved before the ad can deliver. Ensure the order is eligible for approval.

Output: Order not approved

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] These line items conflict with another line item that has a higher priority. Ensure the priority is set correctly. You can change the priority by selecting a different line item type or adjusting your targeting criteria.

Output: Pre-empted by another ad of higher priority

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] If a line item falls behind, Google DFP may deliver up to 120% of the daily goal until the line item is back on track. The line item that's behind schedule may displace other line items. Ensure that line item settings are correct.

Output: Pre-empted by another same priority ad that was behind schedule

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] The line items have a lower delivery priority than the winning line item. Ensure that the priorities of line items are correct. You can change priorities by selecting different line item types.

Output: Priority ranked lower

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] Creatives don't repeat on a single web page. Creatives for a line item serve in as many ad units on the page as the line item is eligible for. Ensure roadblocking rules are set correctly.

Output: Roadblocking rules prevented delivery

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] The line items aren't targeting the same options as the ad unit. If you want a different line item to deliver to the ad unit, ensure that the targeting matches that of the ad unit.

Output: Unmatched targeting or unknown

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Description] Your line item was rejected for a reason other than the ones listed above. Try running the diagnostic tool again. Google DFP will take note of what happened so we can investigate.

Output: Unknown reason

Delivery diagnostics - DFP Small Business Help

Reason why the line item isn't delivering


Input: [Code] 300 (Multiple choices) [Description]

Output: The server has several actions available based on the request. The server may choose an action based on the requestor (user agent) or the server may present a list so the requestor can choose an action.


Input: [Code] 301 (Moved permanently) [Description]

Output: The requested page has been permanently moved to a new location. When the server returns this response (as a response to a GET or HEAD request), it automatically forwards the requestor to the new location. You should use this code to let Googlebot know that a page or site has permanently moved to a new location.


Input: [Code] 302 (Moved temporarily) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [Code] 303 (See other location) [Description]

Output: The server returns this code when the requestor should make a separate GET request to a different location to retrieve the response. For all requests other than a HEAD request, the server automatically forwards to the other location.


Input: [Code] 304 (Not modified) [Description]

Output: The requested page hasn't been modified since the last request. When the server returns this response, it doesn't return the contents of the page. You should configure your server to return this response (called the If-Modified-Since HTTP header) when a page hasn't changed since the last time the requestor asked for it. This saves you bandwidth and overhead because your server can tell Googlebot that a page hasn't changed since the last time it was crawled.


Input: [Code] 305 (Use proxy) [Description]

Output: The requestor can only access the requested page using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.


Input: [Code] 307 (Temporary redirect) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [If you want to ...] Get a site added back to Google [Then ...]

Output: If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning.

Get additional support - Search Console Help


Input: [If you want to ...] Get a page or site removed from Google [Then ...]

Output: Submit a URL removal request.

Get additional support - Search Console Help


Input: [If you want to ...] Report spam [Then ...]

Output: Submit a spam report.

Get additional support - Search Console Help


Input: [If you want to ...] Report a copyright violation or the misuse of your content [Then ...]

Output: File a DMCA takedown request.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google to crawl your site more slowly [Then ...]

Output: Request a change in crawl rate.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google that your content is mistakenly being filtered by SafeSearch [Then ...]

Output: Submit a SafeSearch issue.

Get additional support - Search Console Help


Input: Administrative access Invite users to linked accounts Give “Standard” or “Read only” access to linked accounts Remove a user from a linked account only if it’s a user they originally invited View, edit, and manage any part of linked accounts and campaigns For users originally invited by the individual AdWords account, a manager account user can change that user’s access to a higher level. To change this type of user from “administrative” access to a lower level, the manager account user can only assign the user a special “managed” lower level access (“Managed - Standard” or “Managed - Read only”). This allows the user to still be able to unlink from the manager account. Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Link existing accounts and create new linked accounts Unlink other manager accounts and individual AdWords accounts Invite users to the manager Cancel invitations to the manager account sent by other users Remove a user from the manager account only if the user was originally invited by the administrative user Change access level for manager account users

Create an AdWords manager account - AdWords Help

What the manager account user can do in the manager account


Input: Standard access View, edit, and manage any part of linked accounts and campaigns Sign in and run reports for linked accounts Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Browse the manager account

Create an AdWords manager account - AdWords Help

What the manager account user can do in the manager account


Input: Managed-Standard access This access level is assigned when a manager account user lowers another user’s access level from “Administrative” to “Standard,” and that user was originally invited to the account by someone else. View, edit, and manage any part of linked accounts and campaigns Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Browse the manager account Link existing accounts and create new linked accounts Unlink from accounts managed by this manager account

Create an AdWords manager account - AdWords Help

What the manager account user can do in the manager account


Input: Read only access View, sign in, and run reports for linked accounts Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Browse the manager account

Create an AdWords manager account - AdWords Help

What the manager account user can do in the manager account


Input: Managed-Read only access This access level is assigned when a manager account user lowers another user’s access level from “Administrative” or “Standard” to “Read only,” and that user was originally invited to the account by someone else. Sign in and run reports for linked accounts Browse linked accounts Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Browse the manager account Link existing accounts and create new linked accounts Unlink from accounts managed by this manager account

Create an AdWords manager account - AdWords Help

What the manager account user can do in the manager account


Input: Email only access Receive notification emails for linked accounts Receive emailed reports, if added to email list

Output: Receive notification emails for manager account

Create an AdWords manager account - AdWords Help

What the manager account user can do in the manager account


Input: [If you want to ...] Get a site added back to Google [Then ...]

Output: If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning.

Get additional support - Search Console Help


Input: [If you want to ...] Get a page or site removed from Google [Then ...]

Output: Submit a URL removal request.

Get additional support - Search Console Help


Input: [If you want to ...] Report spam [Then ...]

Output: Submit a spam report.

Get additional support - Search Console Help


Input: [If you want to ...] Report a copyright violation or the misuse of your content [Then ...]

Output: File a DMCA takedown request.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google to crawl your site more slowly [Then ...]

Output: Request a change in crawl rate.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google that your content is mistakenly being filtered by SafeSearch [Then ...]

Output: Submit a SafeSearch issue.

Get additional support - Search Console Help


Input: [Code] 400 (Bad request) [Description]

Output: The server didn't understand the syntax of the request.


Input: [Code] 401 (Not authorized) [Description]

Output: The request requires authentication. The server might return this response for a page behind a login.


Input: [Code] 403 (Forbidden) [Description]

Output: The server is refusing the request. If you see that Googlebot received this status code when trying to crawl valid pages of your site (you can see this on the Crawl Errors page under Health in Google Search Console), it's possible that your server or host is blocking Googlebot's access.


Input: [Code] 404 (Not found) [Description]

Output: The server can't find the requested page. For instance, the server often returns this code if the request is for a page that doesn't exist on the server. If you don't have a robots.txt file on your site and see this status on the Blocked URLs page in Google Search Console, this is the correct status. However, if you do have a robots.txt file and you see this status, then your robots.txt file may be named incorrectly or in the wrong location. (It should be at the top-level of the domain and named robots.txt.) If you see this status for URLs that Googlebot tried to crawl, then Googlebot likely followed an invalid link from another page (either an old link or a mistyped one).


Input: [Code] 405 (Method not allowed) [Description]

Output: The method specified in the request is not allowed.


Input: [Code] 406 (Not acceptable) [Description]

Output: The requested page can't respond with the content characteristics requested.


Input: [Code] 407 (Proxy authentication required) [Description]

Output: This status code is similar 401 (Not authorized); but specifies that the requestor has to authenticate using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.


Input: [Code] 408 (Request timeout) [Description]

Output: The server timed out waiting for the request.


Input: [Code] 409 (Conflict) [Description]

Output: The server encountered a conflict fulfilling the request. The server must include information about the conflict in the response. The server might return this code in response to a PUT request that conflicts with an earlier request, along with a list of differences between the requests.


Input: [Code] 410 (Gone) [Description]

Output: The server returns this response when the requested resource has been permanently removed. It is similar to a 404 (Not found) code, but is sometimes used in the place of a 404 for resources that used to exist but no longer do. If the resource has permanently moved, you should use a 301 to specify the resource's new location.


Input: [Code] 411 (Length required) [Description]

Output: The server won't accept the request without a valid Content-Length header field.


Input: [Code] 412 (Precondition failed) [Description]

Output: The server doesn't meet one of the preconditions that the requestor put on the request.


Input: [Code] 413 (Request entity too large) [Description]

Output: The server can't process the request because it is too large for the server to handle.


Input: [Code] 414 (Requested URI is too long) [Description]

Output: The requested URI (typically, a URL) is too long for the server to process.


Input: [Code] 415 (Unsupported media type) [Description]

Output: The request is in a format not support by the requested page.


Input: [Code] 416 (Requested range not satisfiable) [Description]

Output: The server returns this status code if the request is for a range not available for the page.


Input: [Code] 417 (Expectation failed) [Description]

Output: The server can't meet the requirements of the Expect request-header field.


Input: [Example URL] http://books.google.com/books?vid=OCLC17546826&printsec=frontcover [Page]

Output: Front cover

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?vid=OCLC17546826&printsec=titlepage [Page]

Output: Title page

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?vid=LCCN88005048&printsec=copyright [Page]

Output: Copyright page

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?id=05R7kYOKD0cC&printsec=toc [Page]

Output: Table of contents

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?vid=ISBN0521349931&printsec=index [Page]

Output: Index

Linking to individual titles on Google Books - Books Help


Input: [Example URL] http://books.google.com/books?vid=OCLC17546826&printsec=backcover [Page]

Output: Back cover

Linking to individual titles on Google Books - Books Help


Input: [Geometry Type] All [Description] The type of shape represented in the source data: points lines polygons mixed: multiple shape types unknown: Google Maps Engine was unable to determine the shape [Detail]

Output: Geometry type

Vector details - Google Maps Engine Help


Input: [Geometry Type] All [Description] The number of features in the source data, where a feature is a geometry and a set of attributes. Each geometry can consist of multiple points, multiple polygons, or multiple lines. As an example, an archipelago can be one feature with multiple polygons, each of which represents a single island, or multiple features, each containing one of the islands in the archipelago. [Detail]

Output: Feature count

Vector details - Google Maps Engine Help


Input: [Geometry Type] All [Description] The number of features that generated errors upon upload. Some of the reasons that features are considered bad are as follows: The feature lacks a geometry. The feature's coordinates are out of bounds. Each coordinate in the dataset must have latitude between +90 and -90 and longitude between +180 and -180. The feature cannot be drawn. For example, the feature is specified to be a polygon but the points that constitute it cannot be drawn to form a polygon. The data with the feature is not encoded as specified. The feature does not have all necessary attributes. [Detail]

Output: Bad feature count

Vector details - Google Maps Engine Help


Input: [Geometry Type] All [Description] Each geometry consists of discrete location samples. Vertex count is the sum of such samples. For point data, the sum of all single vertexes. For line data, the sum of all vertex points on all lines. For polygon data, the sum of vertices in the outer and inner loops of all polygons. This value gives some indication of source data complexity. [Detail]

Output: Vertex count

Vector details - Google Maps Engine Help


Input: [Geometry Type] Polygon [Description] If this source data contains multi-polygons, the number present. A multi-polygon is a geometry that consists of multiple polygons, such as a land mass that includes lakes or a lake that includes islands. These inner shapes are listed here as inner lines but can be called inner loops, holes, or cut-outs in other contexts. Note that multiple polygons that constitutes the geometry of a single feature can be treated either as a multi-polygon or as a set of polygons. [Detail]

Output: Multi-polygon count

Vector details - Google Maps Engine Help


Input: [Geometry Type] Line [Description] If this source data contains lines, the number present. [Detail]

Output: Line count

Vector details - Google Maps Engine Help


Input: [Geometry Type] Line [Description] If this source data contains multi-lines, the number present. A multi-line is a geometry that consists of multiple lines, such as a highway whose segments are themselves lines, or a set of all the roads in a county. [Detail]

Output: Multi-line count

Vector details - Google Maps Engine Help


Input: [Geometry Type] Point [Description] If this vector source data contains points, the number present. [Detail]

Output: Point count

Vector details - Google Maps Engine Help


Input: [Geometry Type] All [Description] The East/West and North/South coordinates of the box that encloses this feature on a map. Google Maps Engine creates this box by drawing a North/South line at the most easterly and westerly points of the feature, and by drawing an East/West line at the northernmost and southernmost points of the feature. The bounding box contains all of the geometries in your file. [Detail]

Output: Bounds

Vector details - Google Maps Engine Help


Input: [Geometry Type] All [Description] The largest and smallest altitude values in the source data. [Detail]

Output: Altitude

Vector details - Google Maps Engine Help


Input: [Geometry Type] All [Description] The number of attributes. These attributes are all listed under the Schema header. [Detail]

Output: Attribute count

Vector details - Google Maps Engine Help


Input: [Code] 300 (Multiple choices) [Description]

Output: The server has several actions available based on the request. The server may choose an action based on the requestor (user agent) or the server may present a list so the requestor can choose an action.


Input: [Code] 301 (Moved permanently) [Description]

Output: The requested page has been permanently moved to a new location. When the server returns this response (as a response to a GET or HEAD request), it automatically forwards the requestor to the new location. You should use this code to let Googlebot know that a page or site has permanently moved to a new location.


Input: [Code] 302 (Moved temporarily) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [Code] 303 (See other location) [Description]

Output: The server returns this code when the requestor should make a separate GET request to a different location to retrieve the response. For all requests other than a HEAD request, the server automatically forwards to the other location.


Input: [Code] 304 (Not modified) [Description]

Output: The requested page hasn't been modified since the last request. When the server returns this response, it doesn't return the contents of the page. You should configure your server to return this response (called the If-Modified-Since HTTP header) when a page hasn't changed since the last time the requestor asked for it. This saves you bandwidth and overhead because your server can tell Googlebot that a page hasn't changed since the last time it was crawled.


Input: [Code] 305 (Use proxy) [Description]

Output: The requestor can only access the requested page using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.


Input: [Code] 307 (Temporary redirect) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [Then ...] If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning. [If you want to ...]

Output: Get a site added back to Google

Get additional support - Search Console Help


Input: [Then ...] Submit a URL removal request. [If you want to ...]

Output: Get a page or site removed from Google

Get additional support - Search Console Help


Input: [Then ...] Submit a spam report. [If you want to ...]

Output: Report spam

Get additional support - Search Console Help


Input: [Then ...] File a DMCA takedown request. [If you want to ...]

Output: Report a copyright violation or the misuse of your content

Get additional support - Search Console Help


Input: [Then ...] Request a change in crawl rate. [If you want to ...]

Output: Tell Google to crawl your site more slowly

Get additional support - Search Console Help


Input: [Then ...] Submit a SafeSearch issue. [If you want to ...]

Output: Tell Google that your content is mistakenly being filtered by SafeSearch

Get additional support - Search Console Help


Input: [If you want to ...] Get a site added back to Google [Then ...]

Output: If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning.

Get additional support - Search Console Help


Input: [If you want to ...] Get a page or site removed from Google [Then ...]

Output: Submit a URL removal request.

Get additional support - Search Console Help


Input: [If you want to ...] Report spam [Then ...]

Output: Submit a spam report.

Get additional support - Search Console Help


Input: [If you want to ...] Report a copyright violation or the misuse of your content [Then ...]

Output: File a DMCA takedown request.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google to crawl your site more slowly [Then ...]

Output: Request a change in crawl rate.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google that your content is mistakenly being filtered by SafeSearch [Then ...]

Output: Submit a SafeSearch issue.

Get additional support - Search Console Help


Input: [Then ...] If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning. [If you want to ...]

Output: Get a site added back to Google

Get additional support - Search Console Help


Input: [Then ...] Submit a URL removal request. [If you want to ...]

Output: Get a page or site removed from Google

Get additional support - Search Console Help


Input: [Then ...] Submit a spam report. [If you want to ...]

Output: Report spam

Get additional support - Search Console Help


Input: [Then ...] File a DMCA takedown request. [If you want to ...]

Output: Report a copyright violation or the misuse of your content

Get additional support - Search Console Help


Input: [Then ...] Request a change in crawl rate. [If you want to ...]

Output: Tell Google to crawl your site more slowly

Get additional support - Search Console Help


Input: [Then ...] Submit a SafeSearch issue. [If you want to ...]

Output: Tell Google that your content is mistakenly being filtered by SafeSearch

Get additional support - Search Console Help


Input: [Keyboard keys] h then c [Shortcut]

Output: Focus on first element in the conversation list

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Keyboard keys] h then p [Shortcut]

Output: Go into phone mode (same as g then p)

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Keyboard keys] h then m [Shortcut]

Output: Open Hangouts Settings menu

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Keyboard keys] h then a [Shortcut]

Output: Go to Archived Hangouts and focus on first archived Hangout

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Keyboard keys] h then i [Shortcut]

Output: Go to Hangout Invites and focus on first invite

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Keyboard keys] h then q [Shortcut]

Output: Go to Hangouts search box (same as q)

Keyboard shortcuts for Hangouts - Hangouts Help


Input: [Code] 300 (Multiple choices) [Description]

Output: The server has several actions available based on the request. The server may choose an action based on the requestor (user agent) or the server may present a list so the requestor can choose an action.


Input: [Code] 301 (Moved permanently) [Description]

Output: The requested page has been permanently moved to a new location. When the server returns this response (as a response to a GET or HEAD request), it automatically forwards the requestor to the new location. You should use this code to let Googlebot know that a page or site has permanently moved to a new location.


Input: [Code] 302 (Moved temporarily) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [Code] 303 (See other location) [Description]

Output: The server returns this code when the requestor should make a separate GET request to a different location to retrieve the response. For all requests other than a HEAD request, the server automatically forwards to the other location.


Input: [Code] 304 (Not modified) [Description]

Output: The requested page hasn't been modified since the last request. When the server returns this response, it doesn't return the contents of the page. You should configure your server to return this response (called the If-Modified-Since HTTP header) when a page hasn't changed since the last time the requestor asked for it. This saves you bandwidth and overhead because your server can tell Googlebot that a page hasn't changed since the last time it was crawled.


Input: [Code] 305 (Use proxy) [Description]

Output: The requestor can only access the requested page using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.


Input: [Code] 307 (Temporary redirect) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [If you want to ...] Get a site added back to Google [Then ...]

Output: If your site was distributing malware, and is now clean, request a malware review. If your site was showing spam, but is now clean, submit a reconsideration request. If your site was in violation of the Webmaster Guidelines, but is now clean, submit a reconsideration request. If you asked for a page or site to be removed from Google, but you've changed your mind, request reinclusion of the content. If you received a phishing warning but believe that it's actually a legitimate page, report an incorrect phishing warning.

Get additional support - Search Console Help


Input: [If you want to ...] Get a page or site removed from Google [Then ...]

Output: Submit a URL removal request.

Get additional support - Search Console Help


Input: [If you want to ...] Report spam [Then ...]

Output: Submit a spam report.

Get additional support - Search Console Help


Input: [If you want to ...] Report a copyright violation or the misuse of your content [Then ...]

Output: File a DMCA takedown request.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google to crawl your site more slowly [Then ...]

Output: Request a change in crawl rate.

Get additional support - Search Console Help


Input: [If you want to ...] Tell Google that your content is mistakenly being filtered by SafeSearch [Then ...]

Output: Submit a SafeSearch issue.

Get additional support - Search Console Help


Input: Ahead of schedule [Description] Delivery for these line items has slowed to ensure that they don’t overdeliver.

Output: Ensure that the flight dates, quantity goals, and frequency caps are correct.

Delivery diagnostics - DFP Small Business Help


Input: Current time outside of dayparting window [Description] These line items were targeted to times of day different than the ones targeted by the ad unit.

Output: Ensure the dayparting settings are correct.

Delivery diagnostics - DFP Small Business Help


Input: Delivery goals reached [Description] These line items have stopped serving because they reached their quantity goals or their end date has passed.

Output: If you need to restart the line item, you must copy it and give it new start and end dates.

Delivery diagnostics - DFP Small Business Help


Input: Frequency cap reached [Description] These line items have hit the limit for how many times they can be delivered to the same user within the established time period.

Output: Ensure the frequency capping settings are correct.

Delivery diagnostics - DFP Small Business Help


Input: Incompatible start or end date [Description] The flight dates of these line items don’t match the targeting settings of the ad unit.

Output: Ensure that the flight dates of the line item you want to deliver match the flight dates of the ad unit.

Delivery diagnostics - DFP Small Business Help


Input: Limited by number of ads per page [Description] There aren't enough ad slots on the page to accommodate all of the creatives the line items are set to deliver.

Output: Ensure the number of creatives is equal to or less than the number of ad slots on the page.

Delivery diagnostics - DFP Small Business Help


Input: Line item not active [Description] The line items haven't started running either because their flight dates and times haven't started yet or the line items haven't been activated.

Output: See Line item isn't delivering ads to troubleshoot the problem.

Delivery diagnostics - DFP Small Business Help


Input: Line item not ready [Description] The line items need creatives, are paused or cancelled, or their inventory was released.

Output: Add creatives, check why they were paused or cancelled, or check why their inventory was released.

Delivery diagnostics - DFP Small Business Help


Input: No active right-sized creative associated [Description] The line items don't have creatives that match the sizes of the ad slots on the page.

Output: Add at least one creative that has the same size as an ad unit on the page.

Delivery diagnostics - DFP Small Business Help


Input: Not targeting any active ad units [Description] The line items aren't targeting any of the ad units on the page.

Output: Check the line item's inventory targeting and ensure it's targeting at least one of the ad units on the page.

Delivery diagnostics - DFP Small Business Help


Input: Not targeting any active placements [Description] The line items aren't targeting any placements assigned to this web page.

Output: Check the line item's inventory targeting and ensure it's targeting at least one of the placements assigned to this web page.

Delivery diagnostics - DFP Small Business Help


Input: Order not approved [Description] The order that contains the line items must be approved before the ad can deliver.

Output: Ensure the order is eligible for approval.

Delivery diagnostics - DFP Small Business Help


Input: Pre-empted by another ad of higher priority [Description] These line items conflict with another line item that has a higher priority.

Output: Ensure the priority is set correctly. You can change the priority by selecting a different line item type or adjusting your targeting criteria.

Delivery diagnostics - DFP Small Business Help


Input: Pre-empted by another same priority ad that was behind schedule [Description] If a line item falls behind, Google DFP may deliver up to 120% of the daily goal until the line item is back on track. The line item that's behind schedule may displace other line items.

Output: Ensure that line item settings are correct.

Delivery diagnostics - DFP Small Business Help


Input: Priority ranked lower [Description] The line items have a lower delivery priority than the winning line item.

Output: Ensure that the priorities of line items are correct. You can change priorities by selecting different line item types.

Delivery diagnostics - DFP Small Business Help


Input: Roadblocking rules prevented delivery [Description] Creatives don't repeat on a single web page. Creatives for a line item serve in as many ad units on the page as the line item is eligible for.

Output: Ensure roadblocking rules are set correctly.

Delivery diagnostics - DFP Small Business Help


Input: Unmatched targeting or unknown [Description] The line items aren't targeting the same options as the ad unit.

Output: If you want a different line item to deliver to the ad unit, ensure that the targeting matches that of the ad unit.

Delivery diagnostics - DFP Small Business Help


Input: Unknown reason [Description] Your line item was rejected for a reason other than the ones listed above.

Output: Try running the diagnostic tool again. Google DFP will take note of what happened so we can investigate.

Delivery diagnostics - DFP Small Business Help


Input: [Example URL] http://books.google.com/books?vid=OCLC17546826&printsec=frontcover [Page]

Output: Front cover


Input: [Example URL] http://books.google.com/books?vid=OCLC17546826&printsec=titlepage [Page]

Output: Title page


Input: [Example URL] http://books.google.com/books?vid=LCCN88005048&printsec=copyright [Page]

Output: Copyright page


Input: [Example URL] http://books.google.com/books?id=05R7kYOKD0cC&printsec=toc [Page]

Output: Table of contents


Input: [Example URL] http://books.google.com/books?vid=ISBN0521349931&printsec=index [Page]

Output: Index


Input: [Example URL] http://books.google.com/books?vid=OCLC17546826&printsec=backcover [Page]

Output: Back cover


Input: [Macro] %a [Name] Host name

Output: Expands into http://pubads.g.doubleclick.net.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %c [Name] Click

Output: Works the same as a double-escaped DoubleClick for Publishers click macro.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %e [Name] Expand

Output: The various expand macros will show the IDs of entities connected with the line item and creative being served and the ad unit to which it's being served. The inventory hierarchy in DoubleClick for Publishers is different from the hierarchy in legacy DART for Publishers, so the way the expand macros identify inventory is also different. The %e expand macros are fully supported in DoubleClick for Publishers, as described below.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %g [Name] Geo

Output: Works the same as in legacy DART for Publishers. However, the geographic data used for expanding this macro is no longer updated and may be out of date. Values for area codes, postal codes, DMAs, and even some countries may have changed.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %h [Name] File server

Output: Only works for creatives trafficked in legacy DART for Publishers.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %i [Name] Viewed impression

Output: Works the same as an unescaped viewed impression macro. However, there is no automatic ad deactivation in DoubleClick for Publishers when the viewed impression macro is not included in the creative code for interstitials.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %k [Name] Keyword

Output: Not supported with Google Publisher Tags.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %m [Name] Match code

Output: Not supported.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %n [Name] Cache-busting (random number)

Output: Works the same as the DoubleClick for Publishers cache-busting macro.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %p [Name] Pattern match

Output: Not supported with Google Publisher Tags.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %s [Name] Site name

Output: Expands to the name of the highest-level ad unit above the ad unit where the line item is being served.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %t [Name] Target window

Output: Works the same as the DoubleClick for Publishers target window macro.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Macro] %u [Name] Destination URL

Output: Works the same as the escaped DoubleClick for Publishers destination URL macro.

DFP macros - DoubleClick for Publishers Help

How the legacy macro works with DoubleClick for Publishers


Input: [Detail] Geometry type [Geometry Type] All [Description]

Output: The type of shape represented in the source data: points lines polygons mixed: multiple shape types unknown: Google Maps Engine was unable to determine the shape

Vector details - Google Maps Engine Help


Input: [Detail] Feature count [Geometry Type] All [Description]

Output: The number of features in the source data, where a feature is a geometry and a set of attributes. Each geometry can consist of multiple points, multiple polygons, or multiple lines. As an example, an archipelago can be one feature with multiple polygons, each of which represents a single island, or multiple features, each containing one of the islands in the archipelago.

Vector details - Google Maps Engine Help


Input: [Detail] Bad feature count [Geometry Type] All [Description]

Output: The number of features that generated errors upon upload. Some of the reasons that features are considered bad are as follows: The feature lacks a geometry. The feature's coordinates are out of bounds. Each coordinate in the dataset must have latitude between +90 and -90 and longitude between +180 and -180. The feature cannot be drawn. For example, the feature is specified to be a polygon but the points that constitute it cannot be drawn to form a polygon. The data with the feature is not encoded as specified. The feature does not have all necessary attributes.

Vector details - Google Maps Engine Help


Input: [Detail] Vertex count [Geometry Type] All [Description]

Output: Each geometry consists of discrete location samples. Vertex count is the sum of such samples. For point data, the sum of all single vertexes. For line data, the sum of all vertex points on all lines. For polygon data, the sum of vertices in the outer and inner loops of all polygons. This value gives some indication of source data complexity.

Vector details - Google Maps Engine Help


Input: [Detail] Multi-polygon count [Geometry Type] Polygon [Description]

Output: If this source data contains multi-polygons, the number present. A multi-polygon is a geometry that consists of multiple polygons, such as a land mass that includes lakes or a lake that includes islands. These inner shapes are listed here as inner lines but can be called inner loops, holes, or cut-outs in other contexts. Note that multiple polygons that constitutes the geometry of a single feature can be treated either as a multi-polygon or as a set of polygons.

Vector details - Google Maps Engine Help


Input: [Detail] Line count [Geometry Type] Line [Description]

Output: If this source data contains lines, the number present.

Vector details - Google Maps Engine Help


Input: [Detail] Multi-line count [Geometry Type] Line [Description]

Output: If this source data contains multi-lines, the number present. A multi-line is a geometry that consists of multiple lines, such as a highway whose segments are themselves lines, or a set of all the roads in a county.

Vector details - Google Maps Engine Help


Input: [Detail] Point count [Geometry Type] Point [Description]

Output: If this vector source data contains points, the number present.

Vector details - Google Maps Engine Help


Input: [Detail] Bounds [Geometry Type] All [Description]

Output: The East/West and North/South coordinates of the box that encloses this feature on a map. Google Maps Engine creates this box by drawing a North/South line at the most easterly and westerly points of the feature, and by drawing an East/West line at the northernmost and southernmost points of the feature. The bounding box contains all of the geometries in your file.

Vector details - Google Maps Engine Help


Input: [Detail] Altitude [Geometry Type] All [Description]

Output: The largest and smallest altitude values in the source data.

Vector details - Google Maps Engine Help


Input: [Detail] Attribute count [Geometry Type] All [Description]

Output: The number of attributes. These attributes are all listed under the Schema header.

Vector details - Google Maps Engine Help


Input: Ahead of schedule Ensure that the flight dates, quantity goals, and frequency caps are correct. [Description]

Output: Delivery for these line items has slowed to ensure that they don’t overdeliver.

Delivery diagnostics - DFP Small Business Help


Input: Current time outside of dayparting window Ensure the dayparting settings are correct. [Description]

Output: These line items were targeted to times of day different than the ones targeted by the ad unit.

Delivery diagnostics - DFP Small Business Help


Input: Delivery goals reached If you need to restart the line item, you must copy it and give it new start and end dates. [Description]

Output: These line items have stopped serving because they reached their quantity goals or their end date has passed.

Delivery diagnostics - DFP Small Business Help


Input: Frequency cap reached Ensure the frequency capping settings are correct. [Description]

Output: These line items have hit the limit for how many times they can be delivered to the same user within the established time period.

Delivery diagnostics - DFP Small Business Help


Input: Incompatible start or end date Ensure that the flight dates of the line item you want to deliver match the flight dates of the ad unit. [Description]

Output: The flight dates of these line items don’t match the targeting settings of the ad unit.

Delivery diagnostics - DFP Small Business Help


Input: Limited by number of ads per page Ensure the number of creatives is equal to or less than the number of ad slots on the page. [Description]

Output: There aren't enough ad slots on the page to accommodate all of the creatives the line items are set to deliver.

Delivery diagnostics - DFP Small Business Help


Input: Line item not active See Line item isn't delivering ads to troubleshoot the problem. [Description]

Output: The line items haven't started running either because their flight dates and times haven't started yet or the line items haven't been activated.

Delivery diagnostics - DFP Small Business Help


Input: Line item not ready Add creatives, check why they were paused or cancelled, or check why their inventory was released. [Description]

Output: The line items need creatives, are paused or cancelled, or their inventory was released.

Delivery diagnostics - DFP Small Business Help


Input: No active right-sized creative associated Add at least one creative that has the same size as an ad unit on the page. [Description]

Output: The line items don't have creatives that match the sizes of the ad slots on the page.

Delivery diagnostics - DFP Small Business Help


Input: Not targeting any active ad units Check the line item's inventory targeting and ensure it's targeting at least one of the ad units on the page. [Description]

Output: The line items aren't targeting any of the ad units on the page.

Delivery diagnostics - DFP Small Business Help


Input: Not targeting any active placements Check the line item's inventory targeting and ensure it's targeting at least one of the placements assigned to this web page. [Description]

Output: The line items aren't targeting any placements assigned to this web page.

Delivery diagnostics - DFP Small Business Help


Input: Order not approved Ensure the order is eligible for approval. [Description]

Output: The order that contains the line items must be approved before the ad can deliver.

Delivery diagnostics - DFP Small Business Help


Input: Pre-empted by another ad of higher priority Ensure the priority is set correctly. You can change the priority by selecting a different line item type or adjusting your targeting criteria. [Description]

Output: These line items conflict with another line item that has a higher priority.

Delivery diagnostics - DFP Small Business Help


Input: Pre-empted by another same priority ad that was behind schedule Ensure that line item settings are correct. [Description]

Output: If a line item falls behind, Google DFP may deliver up to 120% of the daily goal until the line item is back on track. The line item that's behind schedule may displace other line items.

Delivery diagnostics - DFP Small Business Help


Input: Priority ranked lower Ensure that the priorities of line items are correct. You can change priorities by selecting different line item types. [Description]

Output: The line items have a lower delivery priority than the winning line item.

Delivery diagnostics - DFP Small Business Help


Input: Roadblocking rules prevented delivery Ensure roadblocking rules are set correctly. [Description]

Output: Creatives don't repeat on a single web page. Creatives for a line item serve in as many ad units on the page as the line item is eligible for.

Delivery diagnostics - DFP Small Business Help


Input: Unmatched targeting or unknown If you want a different line item to deliver to the ad unit, ensure that the targeting matches that of the ad unit. [Description]

Output: The line items aren't targeting the same options as the ad unit.

Delivery diagnostics - DFP Small Business Help


Input: Unknown reason Try running the diagnostic tool again. Google DFP will take note of what happened so we can investigate. [Description]

Output: Your line item was rejected for a reason other than the ones listed above.

Delivery diagnostics - DFP Small Business Help


Input: [Code] 300 (Multiple choices) [Description]

Output: The server has several actions available based on the request. The server may choose an action based on the requestor (user agent) or the server may present a list so the requestor can choose an action.


Input: [Code] 301 (Moved permanently) [Description]

Output: The requested page has been permanently moved to a new location. When the server returns this response (as a response to a GET or HEAD request), it automatically forwards the requestor to the new location. You should use this code to let Googlebot know that a page or site has permanently moved to a new location.


Input: [Code] 302 (Moved temporarily) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [Code] 303 (See other location) [Description]

Output: The server returns this code when the requestor should make a separate GET request to a different location to retrieve the response. For all requests other than a HEAD request, the server automatically forwards to the other location.


Input: [Code] 304 (Not modified) [Description]

Output: The requested page hasn't been modified since the last request. When the server returns this response, it doesn't return the contents of the page. You should configure your server to return this response (called the If-Modified-Since HTTP header) when a page hasn't changed since the last time the requestor asked for it. This saves you bandwidth and overhead because your server can tell Googlebot that a page hasn't changed since the last time it was crawled.


Input: [Code] 305 (Use proxy) [Description]

Output: The requestor can only access the requested page using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.


Input: [Code] 307 (Temporary redirect) [Description]

Output: The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.


Input: [Code] 400 (Bad request) [Description]

Output: The server didn't understand the syntax of the request.


Input: [Code] 401 (Not authorized) [Description]

Output: The request requires authentication. The server might return this response for a page behind a login.


Input: [Code] 403 (Forbidden) [Description]

Output: The server is refusing the request. If you see that Googlebot received this status code when trying to crawl valid pages of your site (you can see this on the Crawl Errors page under Health in Google Search Console), it's possible that your server or host is blocking Googlebot's access.


Input: [Code] 404 (Not found) [Description]

Output: The server can't find the requested page. For instance, the server often returns this code if the request is for a page that doesn't exist on the server. If you don't have a robots.txt file on your site and see this status on the Blocked URLs page in Google Search Console, this is the correct status. However, if you do have a robots.txt file and you see this status, then your robots.txt file may be named incorrectly or in the wrong location. (It should be at the top-level of the domain and named robots.txt.) If you see this status for URLs that Googlebot tried to crawl, then Googlebot likely followed an invalid link from another page (either an old link or a mistyped one).


Input: [Code] 405 (Method not allowed) [Description]

Output: The method specified in the request is not allowed.


Input: [Code] 406 (Not acceptable) [Description]

Output: The requested page can't respond with the content characteristics requested.


Input: [Code] 407 (Proxy authentication required) [Description]

Output: This status code is similar 401 (Not authorized); but specifies that the requestor has to authenticate using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.


Input: [Code] 408 (Request timeout) [Description]

Output: The server timed out waiting for the request.


Input: [Code] 409 (Conflict) [Description]

Output: The server encountered a conflict fulfilling the request. The server must include information about the conflict in the response. The server might return this code in response to a PUT request that conflicts with an earlier request, along with a list of differences between the requests.


Input: [Code] 410 (Gone) [Description]

Output: The server returns this response when the requested resource has been permanently removed. It is similar to a 404 (Not found) code, but is sometimes used in the place of a 404 for resources that used to exist but no longer do. If the resource has permanently moved, you should use a 301 to specify the resource's new location.


Input: [Code] 411 (Length required) [Description]

Output: The server won't accept the request without a valid Content-Length header field.


Input: [Code] 412 (Precondition failed) [Description]

Output: The server doesn't meet one of the preconditions that the requestor put on the request.


Input: [Code] 413 (Request entity too large) [Description]

Output: The server can't process the request because it is too large for the server to handle.


Input: [Code] 414 (Requested URI is too long) [Description]

Output: The requested URI (typically, a URL) is too long for the server to process.


Input: [Code] 415 (Unsupported media type) [Description]

Output: The request is in a format not support by the requested page.


Input: [Code] 416 (Requested range not satisfiable) [Description]

Output: The server returns this status code if the request is for a range not available for the page.


Input: [Code] 417 (Expectation failed) [Description]

Output: The server can't meet the requirements of the Expect request-header field.


Input: [Disapproval reason] Online pharmacy certification required Pharmacy Society Registration Required [What does it mean?] Your ad or website is promoting prescription drugs or related products but your account isn't certified by Google. [What do I do now?]

Output: Remove all references to promoting prescription drugs from your ad and website. Alternately, if you're a licensed online pharmacy, you can be certified with Google -- see how to apply above.

Healthcare and medicines - Advertising Policies Help


Input: [Disapproval reason] Targeting does not match policy [What does it mean?] Your ad or website is promoting prescription drugs or related products and even though your account is certified by Google, your ad is targeting a country outside the country that you were certified for. [What do I do now?]

Output: Remove all references to promoting prescription drugs online from your ad and website. Alternatively, you can change your location targeting for your campaigns to match the country where you're certified to advertise your pharmacy. See the section above for more detail around country-specific restrictions for the countries that you're targeting.

Healthcare and medicines - Advertising Policies Help


Input: [Disapproval reason] URL does not match online pharmacy certification [What does it mean?] Your ad or website is promoting prescription drugs or related products, and even though your account is certified by Google, the website that the ad promotes doesn't match the website that's certified by Google. [What do I do now?]

Output: Remove all references to promoting prescription drugs online from your ad and website. Alternatively, you can change your ad to promote the website that was submitted in your certification request. If you'd like to use a new website as an online pharmacy, it must also be certified with Google -- see how to apply above.

Healthcare and medicines - Advertising Policies Help


Input: [Disapproval reason] OTC drugs license number required [What does it mean?] Your ad or website is promoting over-the-counter drugs without a license number, and that's not allowed for at least one country that your campaign targets. [What do I do now?]

Output: Remove all references to over-the-counter drugs without a license number from your ad and website. Alternatively, you can change your location targeting for your campaigns to target only countries where this service is allowed. See the section above for more detail around country-specific restrictions for the countries that you're targeting.

Healthcare and medicines - Advertising Policies Help


Input: [Disapproval reason] Rx drug reference & pharmaceutical manufacturers [What does it mean?] Your ad or website promotes pharmaceutical manufacturers and mentions branded drug names in the ad text, display URL, website, or keywords, and that isn't allowed for at least one country that your campaign targets. [What do I do now?]

Output: When promoting pharmaceutical manufacturers, remove all references to branded drug names in your ad text, display URL, website, and keywords. Alternatively, you can change your location targeting for your campaigns to target only countries where this service is allowed. See the section above for more detail around country-specific restrictions for the countries that you're targeting.

Healthcare and medicines - Advertising Policies Help