Submission Desk[edit]Please propose Signpost stories you want to write (or have already begun writing). Submitted stories are published subject to the approval of the Editor-in-Chief, Smallbones. We value the involvement of Wikipedians, and appreciate your submissions. If you have ideas or questions that don't fit neatly into this framework, don't hesitate to address us on our user talk pages, by email, or as a last resort, on the general Signpost talk page. The Signpost's content guidelines may be useful to aspiring writers; take note, especially, of the statement of purpose section. We encourage you to contact us early in the process of developing a story. Different writers have varying levels of interest in editorial input, and we pride ourselves on finding the right balance with each writer; but in most cases, a brief discussion early on can help all parties shape our expectations, and can help produce a strong finished piece. We aim to support Wikimedians wishing to share news with their peers, and look forward to working with you. Suez Canal problem is fixed[edit]
The Death of Idriss Déby[edit]
A conference on "Dark Matter of Wikipedia"[edit]
Rambling[edit]
Our live chat supporters[edit]
Tales of the Seven Ages of Wikipedia[edit]
Perspectives of a long-time Wikipedia user and editor[edit]
Four billion words[edit]
November AfD report[edit]
Arbitration report[edit]
Notability: Mailboxes[edit]
Why page titles are important, and how you can help[edit]
A Survey of the Wikipedia Cabal[edit]
TITLE Page[edit]
<meta name="robots" content="noindex"><meta name="robots" content="noindex"> The inspection results include the following expandable sections: URL status (live test) Availability (live test) This section of the tool describes whether the page can be indexed by Google. However, a positive result is no guarantee that it will appear in Search results. The page and its structured data must conform to Google's quality and security guidelines. The live URL inspection also doesn't take into account manual actions, security issues, content removals, or temporarily blocked URLs. Availability statusThe section heading includes a short, descriptive reason for the status of the URL, explaining why the URL is or isn't on Google. This will be "URL can be indexed" if the URL is able to be indexed, or a warning or failure value similar to (but not exactly the same as) those listed and described here. See details.The time of the live test.The user agent type used for the live test.Indicates whether your site will allow Google to crawl (visit) the page, or block it with a robots.txt rule. If you don't want to block Google, you should remove the robots.txt block. Note that this is not the same as allowing indexing, which is given by the "Indexing allowed?" value. Read how to fix a blocked page.Whether or not Google could actually get the page from your server. If crawling is not allowed, this field will show a failure. If crawling is allowed, page fetch might still fail for various reasons. See explanations of fetch failures. "Crawl allowed?" indicates whether you want the page to be reachable; "Page fetch" indicates whether, if allowed, Google could actually reach the page.If your page is blocked by robots.txt (see "Crawl allowed"), then "Indexing allowed" will always be "Yes" because Google can't see and respect any noindex directives. Because of this, your page might appear in Search results.is fine here. If your page is one of a set of similar or duplicate pages, we recommend explicitly declaring the canonical URL. You can declare a canonical URL in several ways: a <link rel="canonical"> tag, an HTTP header, a sitemap, or a few other methods. There is no guarantee that Google will choose this URL, but we will take this into consideration. For AMP pages, the canonical should be the non-AMP version (unless it is a self-canonical AMP). Which index coverage issues are tested in the live test The live test can't detect all page conditions, or predict indexing success with 100% confidence. This is because some types of issues are not, or cannot be tested in real time, such as canonical selection or whether a URL was submitted in a sitemap. If a condition is not checked, the live test result might be URL is available to Google, when in fact indexing will fail due to the condition not tested in the live test. Here are a list of indexing issues from the Index Coverage report, and whether they can be tested in the live test: Index statusTested in live test?NotesExcluded by ‘noindex’ tagYesResults shown in the Indexing allowed? field.Blocked by page removal toolNoYou can check this in the Temporary Removals page.Blocked due to unauthorized request (401)YesResults shown in Coverage status and the Page fetch field.Crawled - currently not indexedNo Discovered - currently not indexedNo Alternate page with proper canonical tagNoInformation about Google's canonical choice is only determined at indexing time.Duplicate without user-selected canonicalNoInformation about Google's canonical choice is only determined at indexing time.Duplicate, Google chose different canonical than userNoInformation about Google's canonical choice is only determined at indexing time.Not found (404)YesResults shown in Coverage status and the Page fetch field.Page with redirectYesResults shown in Page fetch field.Soft 404NoClick View tested page to see how Google renders the page for indexing. Very low content pages can be classified as soft 404s during indexing. Learn more, and how to fix.Duplicate, submitted URL not selected as canonicalNoInformation about Google's canonical choice is only determined at indexing time. Additionally, the live test does not determine whether a URL was submitted using a sitemap.Blocked due to access forbidden (403)YesResults shown in the Page fetch field.Blocked due to other 4xx issueYesResults shown in Coverage status and the Page fetch field.Page indexed without contentNo Indexed, though blocked by robots.txtYesResults shown in Coverage status and several other fields in that section.Submitted URL seems to be a Soft 404No‡Click View tested page to see how Google renders the page for indexing. Very low content pages can be classified as soft 404s during indexing. Learn more, and how to fix.Submitted URL returns unauthorized request (401)Yes‡Results shown in Coverage status and the Page fetch field.Submitted URL not found (404)Yes‡Results shown in Coverage status and the Page fetch field.Submitted URL returned 403Yes‡Results shown in the Page fetch field.Submitted URL blocked due to other 4xx issueYes‡Results shown in Coverage status and the Page fetch field.Submitted URL marked ‘noindex’Yes‡Results shown in the Indexing allowed? field.Submitted URL blocked by robots.txtYes‡Results shown in Coverage status and several other fields in that section.Redirect errorYesResults shown in Page fetch field.Server error (5xx)Yes, but...Your page might not have server errors during the live test, but a server error can occur during actual indexing. Success in the live test is not a guarantee of success later. ‡The live test does not verify whether a URL was submitted in a sitemap. Therefore, indexing issues will be evaluated without any consideration about whether or not they were submitted. Enhancements (Mobile usability, AMP, and more) (live test) Additional response data (live test) View the rendered page You can view a screenshot of the rendered page as Googlebot sees it. This is useful for confirming that all elements of the page are present and appear as you intend. Differences might be the result of resources that are blocked to Googlebot. A screenshot is available only for the live URL test with a successful test result. Screenshots are not available for the indexed URL, or for non-successful fetches of the live test. The page must be reachable to generate a screenshot. If your page is behind a firewall, you can expose it to the URL Inspection tool using a tunnel. To view the rendered page: Inspect the homepage of your site.Click Test live URL on the index results page.Click View tested page on the page verdict card to open additional information panels. If this option is not available it is typically because the page cannot be reached for the live test.Click the Screenshot tab.Request (re)indexing You can request that an inspected URL be indexed by Google. Indexing can take up to a week or two; you can check the progress using this tool. Some caveats when requesting indexing: Indexing typically takes only a day or so, but can take much longer in some cases.Submitting a request does not guarantee that the page will appear in the Google Index.There is a daily limit to how many index requests you can submit. If you want many pages indexed, try submitting a sitemap to Google. To request indexing for a URL: Inspect the page URL.Click Request indexing on the inspection result page for the URL. If the page passes a quick check to test for immediate indexing errors, it will be submitted to the indexing queue. You cannot request indexing if the page is considered to be non-indexable in the live test. To request indexing of many new or updated pages, your best choice is to submit a sitemap, with the updated pages marked by <lastmod>. Troubleshoot a missing page If you think your page hasn't been indexed, here's how to verify and troubleshoot the issue. Check the index status of the page. Inspect the URL, either by entering the URL in the inspection URL textbox, or by clicking the inspect button shown next to a URL in one of the other Search Console reports (you might need to hover over a URL to see this button).The initial test results show you Google's information about the URL in the Google index. These Google index results are used to generate search results. Note: This initial page is not a live test of the URL. Live testing is covered later.If the URL status starts with "URL is on Google", then the page should be available in Google Search. You can verify this by searching for the URL in Google. If the page isn't in search results:Check the Manual Actions report and Security Issues report for issues affecting that page. Issues on either report can prevent your page from appearing in search results.Check to see if someone has temporarily blocked the page.If none of the previous issues affect the page, continue debugging the issue as described here.If the URL status is URL is not available to Google, then expand the Availability section.The Availability section header should include a label describing in brief why the URL could not be indexed. See the list of values and possible fix instructions. If the label is URL is unknown to Google, it means that Google hasn't seen that URL before, so you should request that the page be indexed. Indexing typically takes a few days.If Crawl allowed? is "No," that means Google can't crawl the page because of a robots.txt rule, which prevents Google from crawling the page. Read how to test and fix this issue.If Indexing allowed? is "No", that means your site is returning a "noindex" tag or header that prevents Google from indexing the page, which enables it to appear in Google Search results. You'll have to remove this tag or header from the page before Google will index it.If you've changed the page since the crawl time listed, you can test your current version of the page by clicking Test live URL. If the status shown at the top of the page valid, then the page can probably be indexed (note that not all indexing issues can be detected by the live test). Known issues In a few cases, we don't report the sitemap for a page that was submitted in a sitemap. We are working to fix this. Why you should source your plot summaries[edit]
How to write a good DYK hook (by a gal who only sometimes writes good DYK hooks)[edit]
|