robots.txt + translatepress + file_edit

  • Resolved workcy

    (@workcy)


    1 year, 6 months ago

    Heho

    I set translatepress to create subfolders for each language.

    Now the virtual robots.txt getting redirected to /en/robots.txt or /de/robots.txt

    If I create an actual robots.txt on the disk this redirection didn’t happen.

    Now my question is: If I have file_edit disabled in wp_config, does yoast still can edit it? I don’t want to enable it for security reasons and I didn’t found a solution for the automatic redirection of the virtual file.

    From your documentation it seems that yoast require file_edit but I can’t really understand why. It seems .htaccess does get edited without file_edit.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @workcy

    Thanks for reaching out about the robots.txt file on your multilingual site. A quick question: do you have the same content when you visit yoursite.com/robots.txt and yoursite.com/?robots=1?

    Thread Starter workcy

    (@workcy)

    hmmm. robots=1 produces a “too many redirects” error

    EDIT: But if I open /en/?robots=1 then I get the virtual robots.txt
    They are only identical at the moment because I created the robots.txt file yesterday with temporary file_edit enabled over yoast file editor.

    • This reply was modified 1 year, 6 months ago by workcy.
    Plugin Support Maybellyne

    (@maybellyne)

    Thanks for the quick response @workcy!

    Now the virtual robots.txt getting redirected to /en/robots.txt or /de/robots.txt

    This sort of redirect will be done by your multilingual plugin, Translatepress or on the server.

    Also, once you create a physical robots.txt file on the root directory of your site, Yoast SEO shouldn’t write to it.

    Thread Starter workcy

    (@workcy)

    Yoast SEO shouldn’t write to it

    But doesn’t yoast update the robots.txt if I set a page for “no indexing” for search engines? I always wondered why the denied block is always empty

    Setting the page to ‘noindex’ from Yoast SEO metabox or settings interface won’t update the robots.txt. This option simply sets the meta data tag output on the page source to noindex as something below.

    <meta name=”robots” content=”noindex, nofollow” />

    This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘robots.txt + translatepress + file_edit’ is closed to new replies.