Hi, Monika. I'm not sure what admin.google.com is but I use Google Webmaster Tools (Search Console) with a regular, bog-standard Gmail account just fine... validating your web property and adding a sitemap should be very easy!
Ciao, On Fri, May 26, 2017 at 7:11 PM Monika Mevenkamp <[email protected]> wrote: > Tim > > thanks for your answer - yes sitemaps are up and I just fixed my > robots.txt file to allow crawlers in. > > But when I try to log into the Google webmaster tool's > <https://www.google.com/webmasters/#?modal_active=none> search > console, I get the message > > admin.google.com is for G Suite accounts only. Regular Gmail accounts > cannot be used to sign in to admin.google.com. Learn more > <http://www.google.com/support/a/answer/6375836?hl=en> > > when I learn more I get to a page that offers a 14 day trial. Is there > another way to invite Google to crawl my instance ? > > It looks to me that Google now wants to make money on both ends, webmaster > support and advertising. > > Monika > > ________________ > Monika Mevenkamp > [email protected] > > http://mo-meven.tumblr.com/ > http://mcmprogramming.com/mo.meven/ > > > > On May 25, 2017, at 4:37 PM, Tim Donohue <[email protected]> wrote: > > Hi Monika, > > We are in touch with Google Scholar staff on a regular basis (at least > yearly), and they forward along any issues they are seeing with DSpace > sites so that we can resolve them. Essentially, out of the box, DSpace is > Google Scholar compliant. So, you need not modify any of the default > settings, unless you have custom metadata fields you wish to make available > to Google Scholar, etc. > > Google Scholar used to have a published way of requesting an index of the > site. But, I'm no longer finding it among their resources. However, I know, > like Google crawlers, the Google Scholar crawlers are pretty smart about > finding *any* public repository out there that is linked to from > elsewhere. Also, you could use Google Webmaster tools to notify the Google > crawlers (and I believe Google Scholar is notified as well). > > Also, we have a reference in the DSpace documentation regarding optimizing > SEO for DSpace. Google Scholar highly recommends enabling Sitemaps in > DSpace (as it makes it much easier to locate all the content): > https://wiki.duraspace.org/display/DSDOC5x/Search+Engine+Optimization > > - Tim > > > On Thu, May 25, 2017 at 3:17 PM Monika Mevenkamp <[email protected]> > wrote: > >> I want Google Scholar to come and index my DSpace instance (v5) >> The instance generates the meta tags shown below >> >> The Google Scholar requirements documentation at scholar/inclusion >> <https://scholar.google.com/intl/us/scholar/inclusion.html#indexing> talks >> about citation_* and DC.* meta tags. It does not mention DCTERMS.* tags. On >> the other hand the documentation says: DSpace is fine. >> >> So, do I have to adjust the out of the box settings ? >> >> I could not find anything about nominating my instance to be indexed with >> Google Scholar. >> Can I do that so Google Scholar knows to come crawling ? >> >> Monika >> >> >> <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/";> >> <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/";> >> <meta name="DC.contributor.author" content="Tkacik, Gasper"> >> <meta name="DC.contributor.author" content="Walczak, Aleksandra M"> >> <meta name="DC.contributor.author" content="Bialek, William"> >> <meta name="DCTERMS.dateAccepted" content="2017-04-04T20:19:12Z" scheme=" >> DCTERMS.W3CDTF"> >> <meta name="DCTERMS.available" content="2017-04-04T20:19:12Z" scheme=" >> DCTERMS.W3CDTF"> >> <meta name="DCTERMS.issued" content="2012-04-05" xml:lang="en_US" scheme >> ="DCTERMS.W3CDTF"> >> <meta name="DCTERMS.bibliographicCitation" content="Tkacik, Gasper, >> Walczak, Aleksandra M, Bialek, William. (2012). Optimizing information flow >> in small genetic networks. III. A self-interacting gene. PHYSICAL REVIEW E, >> 85 (10.1103/PhysRevE.85.041903)" xml:lang="en_US"> >> <meta name="DC.identifier" content="1539-3755"> >> <meta name="DC.identifier" content=" >> http://arks.princeton.edu/ark:/88435/pr19w4b"; scheme="DCTERMS.URI"> >> <meta name="DCTERMS.abstract" content="Living cells must control the >> reading out or “expression” of information encoded in their genomes, and >> this regulation often is mediated by transcription factors—proteins that >> bind to DNA and either enhance or repress the balboa… t." xml:lang="en_US >> "> >> <meta name="DCTERMS.extent" content="041903-1 - 041903-16" xml:lang=" >> en_US"> >> <meta name="DC.language" content="en" xml:lang="en_US" scheme=" >> DCTERMS.RFC1766"> >> <meta name="DCTERMS.isPartOf" content="PHYSICAL REVIEW E" xml:lang="en_US >> "> >> <meta name="DC.rights" content="Author's manuscript" xml:lang="en_US"> >> <meta name="DC.title" content="Optimizing information flow in small >> genetic networks. III. A self-interacting gene" xml:lang="en_US"> >> <meta name="DC.type" content="Journal Article" xml:lang="en_US"> >> <meta name="DC.identifier" content="doi:10.1103/PhysRevE.85.041903"> >> <meta name="DC.date" content="2012-04-05" xml:lang="en_US" scheme=" >> DCTERMS.W3CDTF"> >> <meta name="citation_author" content="Tkacik, Gasper"> >> <meta name="citation_author" content="Walczak, Aleksandra M"> >> <meta name="citation_author" content="Bialek, William"> >> <meta name="citation_issn" content="1539-3755"> >> <meta name="citation_date" content="2012-04-05"> >> <meta name="citation_abstract_html_url" content=" >> http://oar.princeton.edu/jspui/handle/88435/pr19w4b";> >> <meta name="citation_language" content="en"> >> <meta name="citation_pdf_url" content=" >> http://oar.princeton.edu/jspui/bitstream/88435/pr19w4b/1/1112.5026v1.pdf"; >> > >> <meta name="citation_keywords" content="Journal Article"> >> <meta name="citation_title" content="Optimizing information flow in >> small genetic networks. III. A self-interacting gene”> >> >> >> ________________ >> Monika Mevenkamp >> Digital Repository Infrastructure Developer >> Princeton University >> Phone: 609-258-4161 <(609)%20258-4161> >> Skype: mo-meven >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > -- > > Tim Donohue > Technical Lead for DSpace & DSpaceDirectDuraSpace.org | DSpace.org | > DSpaceDirect.org > > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Alan Orth [email protected] https://picturingjordan.com https://englishbulgaria.net https://mjanja.ch -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
