For better SEO, I'd like to generate the "description" and "keywords" metatags in the HTML output produced by Doxygen. I've noticed that these metatags are present in the original Doxygen HTML documentation. But I cannot figure out how to supply these metatags in my own projects. Also, I'd like to use different metatags in different HTML pages (the Doxygen documentation merely repeats the same metatags in all HTML pages.)
Related
We have a multilanguage single page html site. What we do is, we take the browser's language on document.ready and translate page content in that language and also we have given facility to change the language so that the user can view the page in that language.
<h1 key="key_title"><h1>
This is a tag in our site. translate() function will set html or text of this tag languagewise. And so all the tags are translated.
The question is how can we manage meta kewords and description in multiple languages? The meta tags are by default in english. And are changed dynamically. We have solutions that suggests using Transcribe. Is there is any easy way.?
If you translate on document.ready, you could extend your javascript code to modify the meta keyword and description tags too.
See this example: https://stackoverflow.com/a/47212820/520957
I am talking about the Open Graph tag here. Can I put the og meta tag anywhere on the page?
I want to use my detail page image for the og tag, the easiest solution is putting the og:image tag in the body of my page.
Open Graph meta tags should always be nested between <head> tags.
To turn your web pages into graph objects, you need to add basic
metadata to your page. We've based the initial version of the protocol
on RDFa which means that you'll place additional <meta> tags in the
<head> of your web page.
http://ogp.me/#metadata
Additionally, keep in mind that order of the tags matters, especially when dealing with array tags (which includes og:image).
Open Graph Tag should be always always be placed on header tag until knowledge goes.. People please correct me if I am wrong..
Where should I put schema.org tags?
I have 3 options:
at detail page of article
at category page where are articles of
category
at search page
Should I put schema.org tags on all these pages or?
You can use Schema.org on all pages.
Various consumers might find it useful. Why should they have to visit a specific page to see your Schema.org markup for content they already see?
Just make sure that you don’t create several items for the same thing on the same page, unless you denote them as being about the same thing (e.g., with Microdata’s itemid or by using the same subject URI in RDFa).
You could use mainEntity/mainEntityOfPage to denote which item the page is primarily about.
Is There any way so that i change the snippet created by google indexing,so that it Drives more Traffic,Making it more Relavent which i can show to the users
Google will choose your search results snippets from the following places (not necessarily in this order):
The page's Meta Description tag
The page's Open Directory Project (ODP) Listing
Page content relevant to the search query
If you do not want Google to use the ODP listing's description then you can tell them not to do so with the following Meta tag:
<meta name="robots" content="NOODP">
If you want to encourage Google to use your Meta Description tag then make sure it is unique to each page. Also make sure it contains an accurate description of the page's content.
In thew absence of an ODP description and Meta Description tag, Google will use a portion of the page's text as the description. This text will contain the closest matches to the search query. I have not seen any official limit to how long this can be but a couple of sentences seems about right.
On a related note, if you don't want a snippet to be shown with a particular page you can use the following Meta tag to prevent one from being shown:
<meta name="robots" content="nosnippet">
See this blog post for Google's tips on using the meta description tag.
According to this site, "The meta description should typically be at most 145 to 150 characters in length as these are the maximum number of characters typically displayed at Yahoo! and Google, respectively."
If you put a MainPage.dox file in Doxygen's search path, it will add it to the output in Doxygen/html above the source documentation. But can you have multiple files like MainPage.dox? Or are you limited to one?
Doxygen will recognize and parse any file that has a *.dox extension and include it in the resulting documentation. What those files will produce is dictated by the doxygen comments located in the file. For example, if you want to modify the main page, you'll need a comment like:
/**
* #mainpage
* Documentation you want to occur on the main page.
*/
You can also create documentation that should appear on other pages using this technique:
/**
* #page another_page Another Page
* Documentation that will occur on another page.
*/
Assuming HTML output, this form will create a file named another_page.html at the same level as index.html. The title will be Another Page, and the content referenced will follow. An additional tab will also be produced named Related Pages which will have links to all of the related pages created in this manner.
Blocks like this can occur in any file that doxygen parses (including header or source files), and can contain definitions for multiple pages (both of the comments above could be in a single file). The file they're located in does not have an impact on the output that is produced.
As of 1.8.4, .md markdown pages can also be included as separate pages without need for .dox C++ like comments /** */ if they are to be considered by doxygen according to your INPUT and FILE_PATTERNS configs.
One difference between using .md and .dox is that .md files produce a Related page with the same name as the basename without extension of the .md file, while .dox only produces pages with names given by \page commands.
It is still possible to use \page commands from .md files.
For example, if file md_page.md contains:
Inside md_page.
\page md_page2 Md Page 2
Inside md_page2
this will generate 2 pages under "Related Pages" entitled:
md_page
Md Page 2